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!
You may wish to put in a ticket with TASK. We had an issue recently where our annual brochure (a big extraction) was simply not completing. The cause wound up being our extraction database simply being too large. Tessitura was able to help us essentially trim old extraction results until our database was about 90% smaller, and this allowed the extraction to complete. Even trimming the database wound up being a mammoth task that took over a week to finish.