Performance Tunning SQL Selects

  • I have been given an SQL Select statment that runs with poor performance.   It has CASEs in the Select, INs in the Where, and Joins.  Where do I start when trying to (1) Define what part of that query is hurting it most, (2) improve performance?  Making a flat table for query access is not an option.  The database load 3 million records a week.

    Thanks for any feedback you can provide.

  • Get the performance plan from Query Analyzer. CTRL-K should turn it on. Run your query and then look at the performance plan. It will clue you in to the sections of your query that are taking the most time (%-wise). Focus on these and re-run until you think you have an optimal query.

  • SHowPlanOn I've got it on, however:

    Does the 98% Dimension table read concern me.  Is it using 90% Processor Time?  This is a simple select with a where and a group by pulling back 1 record .. what does the system consider a scalor and a bookmark in that mix?

    PlanShown

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply