The activity monitor in sql2k8 allows us to see the most expensive queries. Ok, that's cool, 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!
(DELL)Quest SQL Optimizer for SQL Server 9.0 introduces Find SQL module which allow users to locate the most resource-intensive SQL in your SQL Server. https://support.quest.com/softwaredownloads.aspx?pr=268445262
There's a new tool, Performance Studio in SQL Server 2008 which builds on top of Dynamic Management Views maintained automatically by the server, that gives an overview of the server performance. It worth checking out.
The Following script gives you the result.
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).
Use SQL Server Profiler (on the tools menu in SSMS) to create a trace that logs these events:
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).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.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:
Then you can run a query to aggregate the data such as this one:
Once you have identified the costly queries, you can generate and examine the actual execution plans.
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.