February 9, 2006 at 9:53 am
Hello,
Could someone give me some general guidance on what types of things one should take note of when viewing/interpreting the estimated execution plan for a query? For example, what differentiates a good plan from a bad plan? Also, what types of things could a developer do to the query to address whatever the plan shows as least optimal? I know my question is extremely general in nature, but I am trying to become better at tuning queries that take a long time to process. Thank you.
February 9, 2006 at 10:21 am
Welcome.
Have a look at
http://www.sql-server-performance.com/query_execution_plan_analysis.asp
Performance is mostly based on the amount of reads (I/O) and then cpu/duration.
If possible avoid the use of cursors(very important),record by record based solutions and use set-based solutions instead (sometimes needs a new way of thinking) instead of record by record based solutions.
February 9, 2006 at 11:33 am
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply