dajonx (1/14/2011)
Thank you, David!I understand that all of the categories are important, but is there some sort of "ranking" that I could use as a guideline? In your example, you said that I probably wouldn't want CPU time to go up which I agree. So, I guess in a way, you could rank CPU time as #1 in terms of importance?
I completely understand that there will have to be some sort of give and take. I just want to be certain that my order of importance is correct. By the way, I know I have a LOT to read to improve myself in this area of query tuning.
Personally, execution time (from call to results) is almost always my priority. That can encapsulate a lot, so the rest of them are on a per-issue basis. They will get ranked according to your system's usage more than any 'set' list, as David mentioned above. If you've got a heavy transactional system, disk I/O will become important, where as if you're doing a ton of sorting CPU and memory may be more important.
It's a matter of isolating your primary bottlenecks and working to make sure they don't get overwhelmed.
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