Capturing, Measuring, and Replaying a Workload Using SQL Profiler - Professional SQL Server 2005 Performance Tuning - page 334

--FROM dbo.DS2_40Threads_20Min_3SecThink
WHERE eventclass IN (10,12)
GROUP BY SUBSTRING(textData, 1, 25)
ORDER BY Ave_Duration_ms DESC

As shown in Figure 10-11, the Avg_Duration_ms column can be used to gauge average response time
for each user database transaction. For example, the response time for the BROWSE_BY_CATEGORY is
about 30 milliseconds.

Here is the workload's overall system resource utilization:

Total CPU (Millisecond): 988,086

❑

Reads: 11,540,281

❑

Writes: 2,197

❑

Table 10-1 shows the user transactions from the original workload.

Table 10-1: User Transactions in the Original Workload

RPC and SQL Batch
Events

Counts Avg. Duration (ms) Avg. CPU (ms) Avg. Reads Avg.
Writes

exec PURCHASE
@customerid

15,486 80 33 577 0

Exec BROWSE_BY_
CATEGORY @

15,448 30 21 68 0

exec
BROWSE_BY_ACTOR
@bat

15,399 21 2 7 0

exec
BROWSE_BY_TITLE
@bat

15,539 18 1 0 0

--'password' was
found i

15,481 7 0 38 0

select PROD_ID, PRICE
fro

15,482 5 3 53 0

NewPerformanceReference for aWorkloadReplay
SQL 2000/2005 Profiler does not replay trace events at the same speed that they originally occurred.
To compare the same workload in different testing environments (hardware, software) you need to
re-establish the workload performance reference.