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

Figure 10-23

Table 10-3: Scenario 2 — Results

Testing Server Replay Time Replay Time in Seconds Performance Comparison

TestServerL 17 min 10 sec 1030 1 (reference)

TestServerM 7 min 32 sec 452 2.2 times faster

TestServerH 3 min 52 sec 231 4.4 times faster

Scenario 3: ReplayingMultipleWorkloads on a Target
Server
Wouldn't it be nice if we could replay multiple workloads on a target server to see if the target server
could deliver the expected performance? In this scenario, we will use the SQL Profiler as a client load
driver with multiple replay sessions connecting to a target SQL Server 2005 instance.

There are many ways to set up this testing environment; however, two factors need to be considered.
The first factor is that SQL profiler is not a specialized tool for load testing; replaying a large workload
consumes high CPU. For this reason, we will use a dedicated multi-processor server for SQL Profiler. The
second factor to consider is the network overhead between the two servers. In this scenario, we will put
all servers in the same network segment.