Hello,
When running list/output sets, has anyone experienced issues of run times that last 20-30 mins and/or the list periodically failing in general (application crash)? We've internally come to a conclusion that maybe it has to do with resource bandwidth because sometimes running the same list/output set works after-hours. Another work around is that we run the Execute an Output Set utility.
We usually see the typical errors of "timeout", "cannot find the file specified", or it just crashes.
I'm wondering if any of you have had similar issues or direction on how/if this can be remedied?
Thanks,
Allan
Are any parts of these lists or output sets custom? Definitely with the latter, performance can be a lot worse than you expect because of the way that the output set queries are actually assembled to run.
Do you know how to show the SQL that the list criteria screens generate?
Sometimes when looking at performance questions. I've gone and taken the SQL over to SQL Server Management Studio and plugged the query in there to see if I'm getting the same slow times. This has some times helped me understand which part of the query is running slow.
I'd also open a support ticket on this. The support team is helpful in looking at some of these performance-related issues.
Hmm.. I don't think they are considered custom, but definitely good to know."All of my lists are either created in List Manager, saved from ExtractionManager, or imported. For the most part, I'm using lists created in ListManager."
I suppose we can try running it using the trace tool to extract the SQL. Is that what you're referring to?