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!
Hello,
We just experienced this same problem. A 20K output set took more than 8 hours to process. We were able to reduce the time by running the output set directly on our server vs. a client PC.
Best regards,
Christine Kohls
Director of Development
The Cleveland Museum of Natural History
ckohls@cmnh.org