How Can I Log and Find the Most Expensive Queries?

Hi folks

The activity monitor in sql2k8 allows us to see the most expensive queries. Ok, that's kewl, but is there a way I can log this info or get this info via query analyser? I don't really want to have the Sql Management console open and me looking at the activity monitor dashboard.

I want to figure out which queries are poorly written/schema is poorly designed, etc.

Thanks heaps for any help!

From stackoverflow

• Would the SQL Server Profiler do what you need? I haven't used 2008 yet so I don't know if the tool is still in there but if it is I believe you can set up a trace to log queries that meet specific criteria (such as those that execute and drive CPU up above a certain threshold).

  We've used this on our project and it did a pretty good job of helping us troubleshoot poorly executing queries (though don't leave it on full time, rely on the general Windows Performance Counters for performance health tracking).

  Pure.Krome : hmm.. i've used the profiler heaps, but that doesn't summarise information. it's a line per query type of thing.

• 1. Use SQL Server Profiler (on the tools menu in SSMS) to create a trace that logs these events:

     • RPC:Completed
     • SP:Completed
     • SP:StmtCompleted
     • SQL:BatchCompleted
     • SQL:StmtCompleted

  
  2. You can start with the standard trace template and prune it. You didn't specify whether this was for a specific database or the whole server, if it is for specific Db's, include the DatabaseID column and set a filter to your DB (SELECT DB_ID('dbname')). Make sure the logical Reads data column is included for each event. Set the trace to log to a file. If you are leaving this trace to run unattended in the background, it is a good idea to set a maximum trace file size say 500MB or 1GB if you have plenty of room (it all depends on how much activity there is on the server, so you will have to suck it and see).

  1. Briefly start the trace and then pause it. Goto File->Export->Script Trace Definition and pick your DB version, and save to a file. You now have a sql script that creates a trace that has much less overhead than running through the profiler GUI. When you run this script it will output the Trace ID (usually @ID=2); note this down.

  2. Once you have a trace file (.trc) (either the trace completed due to reaching the max file size or you stopped the running trace using

     EXEC sp_trace_setstatus @ID, 0

     EXEC sp_trace_setstatus @ID, 2

  You can load the trace into profiler, or use ClearTrace (very handy) or load it into a table like so:

  SELECT * INTO TraceTable
  FROM ::fn_trace_gettable('C:\location of your trace output.trc', default)
  

  Then you can run a query to aggregate the data such as this one:

  SELECT COUNT(*) AS TotalExecutions, 
      EventClass, CAST(TextData as nvarchar(2000))
   ,SUM(Duration) AS DurationTotal
   ,SUM(CPU) AS CPUTotal
   ,SUM(Reads) AS ReadsTotal
   ,SUM(Writes) AS WritesTotal
  FROM TraceTable
  GROUP BY EventClass, CAST(TextData as nvarchar(2000))
  ORDER BY ReadsTotal DESC
  

  Once you have identified the costly queries, you can generate and examine the actual execution plans.

  Pure.Krome : cheers mitch! sounds a bit more complex that i thought was required, but i'll most definitely give it a go :) cheers!

  Mitch Wheat : How did you go with your profiler analysis?

  Pure.Krome : Been flat out - i'm expecting to get a chance towards the end of nov .. and then i'll mark the question or ask more q's.

• A late answer...

  Use DMVs to find out. Easier then profiler...

  Pure.Krome : Thanks Glenn! Nice answer also :)

• I had never heard of this tool before, but Microsoft provides a set of reports that do a fantastic job of giving you exactly this - including slowest queries. Check out their Performance Dashboard Reports.

  Not sure if they're SQL 2008-compatible, but worth checking out.