This content has been marked as final. Show 4 replies
Maybe you can solve your problem by building a summary table in your db. You could keep it up to date with triggers or with scheduled updates depending on the complexity and your business needs.
So does anyone have opinions about performance between QueryNew's, Structures and SQL Temp Tables... Input on what they think is fastest? I don't think a summary table would work in this instance because the data is too flexible and ever-changing and there are so many clients it could be run for that the summary table would become repeats of our main db tables.
I think SQL Temp Tables is the more correct approach. I also thnk that it is the
Scanning/filtering data in sql tables sounds like something the database
should be doing?
Changing from QueryNew to a SQL Temp table cut down the largest example of the page processing by 40 seconds. It was taking 52 seconds and now takes 10 seconds.