This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I am looking for extracting and loading 7.4 GB data with 4.5 M records and 124 fields, currently with input/in-DB tool it takes approximately 1 to 1.5 hrs. Can anyone tell me best approach to do that. Anyone tried the connectivity in python tool and doing it with python tool . Please guide.
Is it only the data input that takes that long, or is it the rest of the downstream processing?
Some downstream processes can make it appear that the whole thing slows down, when really a bottleneck down the road holds everything up. Try putting a block until done after your input to see if the input finishes faster, from there you can try optimizing your workflow.
Unfortunately I think this starts bleeding over into SQL management territory. Is it alteryx that's slow, or does it take a similar amount of time from another query tool using the same query (you can pull the query text from the query builder)? If it still takes about an hour in another tool then it's the database that needs optimization, not alteryx.
Database administration isn't my thing but my first thoughts would be: can you optimize the query better? Can you add a primary key to your database to help it search better?
In my Input tool, I am just doing Select * from <table_name>
The same query if I run in SQL server side it takes only 5 minutes to load records
But in Alteryx it takes more than an hour to do it. I am just curious to know if we can do it faster loading or any other alternative or any other tool should I use in alteryx. If you can provide steps would be great help
So the query is fast on the server machine itself (good sign), but is it as fast on your machine? Maybe its a data transport issue? I'm not aware of much inside SQL server, but is there possibly a rate limiting function it's using to try and save itself from getting pounded by a single user?