September 14, 2010 at 10:29 am
Hi, there is a report generated with a proc and it uses a smry tbl (million plus records)... the problem is there is lot of aggregations to be done in the proc. since the date range for the report requested is not fixed (its interactive report) so preaggregations cannot be done and stored before querying.
changes in the table structure can be thought about.
any suggestions/ideas on how to tackle this?
September 14, 2010 at 11:07 am
Any chance you can post the table/index definitions and a query your reports use? Helps us to try to figure out if you've optimized to indexes and the like or if there's some suggestions we can make to help speed up your process.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
September 14, 2010 at 8:17 pm
I agree. A good covering index is the key to getting this type of query to run quickly. How often are these totals requested? Are they a daily request? Once a month? Several times a day? How long is it taking your query to run now?
__________________________________________________
Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply