One of our users has created an Extraction Set that is taking a very long time to complete (like 3-4 hrs). We have no other performance issues with running queries etc., in fact performance across the database has been pretty snappy. This extraction set returns something like 20,000 rows and is linked to an Output Set.
Has anyone else run into issues with Extraction Set performance? I started to do a little digging, but didn't want to spend too much time on this if this is a known issue across multiple organizations (like T-Stats build time for instance).
Thanks!
I have opened a TASK ticket and am troubleshooting this with Tessitura. There are some great tips here also, thanks so much! I will try and update this ticket to let people know the resolution.
The issue was related to a view things, all of which other users in this post pointed out!
We were extracting to a network drive, not a drive on the database server. Moving the extraction folder on the database server sped things up a lot.
Running from a Client on the database server also sped things up.
Finally, when the jobs runs it populates the table tw_extract_cust_info with all the extraction data. It then removes that data once it's complete. However, if the jobs fail this data is not cleared out (neither is the temp job, table, view). So we were running against a table of 700k records with Index fragmentation of 99%. Clearing out this data improved performance massively.