Technical Article

Trace Analysis script

,

Trace files are wonderful because they provide extensive information on what the SQL server is doing during the time that they are running. The main difficulty that one has when reading a trace file using SQL Server Profiler is that the data cannot be sorted or aggregated within that UI. This query allows me to pull in the data from any trace file, then aggregate the trace data by objectName to find average values for CPU Use, Reads, Writes, and duration for each stored procedure. By altering the ORDER BY clause, the worst performing items bubble up to the top of the list.

Before using this script, please be sure to change the trace file name from C:\Temp\MyTrace.trc to the correct name and location for your trace file.

Happy Tuning!

select ObjectName, substring(DatabaseName, 1, 18) as databaseName
, AVG(cpu) as CPUuse
, AVG(reads) as avgReads
, AVG(writes) as avgWrites
, COUNT(EndTime) as Instances
, AVG(duration) as avgDuration
, COUNT(EndTime) * AVG(reads) as CumulativeExpense
from fn_trace_gettable ('C:\temp\MyTrace.trc', DEFAULT) -- change trace file name
group by ObjectName,  substring(DatabaseName, 1, 18)
order by avgReads desc

Rate

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

3 (1)

You rated this post out of 5. Change rating

Share

Join the discussion and add your comment

Share

Rate

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

3 (1)

You rated this post out of 5. Change rating

Related content

External Article

Optimizing Your Query Plans with the SQL Server 2014 Cardinality Estimator

SQL Server 2014 introduces the first major redesign of the SQL Server Query Optimizer cardinality estimation process since version 7.0. The goal for the redesign was to improve accuracy, consistency and supportability of key areas within the cardinality estimation process, ultimately affecting average query execution plan quality and associated workload performance. This paper provides an overview of the primary changes made to the cardinality estimator functionality by the Microsoft query processor team, covering how to enable and disable the new cardinality estimator behavior, and showing how to troubleshoot plan-quality regressions if and when they occur.

2018-06-26

2,974 reads