SQL Server Distributed Replay
The Microsoft SQL Server Distributed Replay feature helps you assess the impact of future SQL Server upgrades. You can also use it to help assess the impact of hardware and operating system upgrades, and SQL Server tuning.
New feature introduced on SQL Server 2012
Benefits of Distributed Replay
Similar to SQL Server Profiler, you can use Distributed Replay to replay a captured trace against an upgraded test environment. Unlike SQL Server Profiler, Distributed Replay is not limited to replaying the workload from a single computer.
Distributed Replay offers a more scalable solution than SQL Server Profiler. With Distributed Replay, you can replay a workload from multiple computers and better simulate a mission-critical workload.
The Microsoft SQL Server Distributed Replay feature can use multiple computers to replay trace data and simulate a mission-critical workload. Use Distributed Replay for application compatibility testing, performance testing, or capacity planning.
Distributed Replay Concepts
The following components make up the Distributed Replay environment:
- Distributed Replay administration tool: A console application, DReplay.exe, used to communicate with the distributed replay controller. Use the administration tool to control the distributed replay.
- Distributed Replay controller: A computer running the Windows service named SQL Server Distributed Replay controller. The Distributed Replay controller orchestrates the actions of the distributed replay clients. There can only be one controller instance in each Distributed Replay environment.
- Distributed Replay clients: One or more computers (physical or virtual) running the Windows service named SQL Server Distributed Replay client. The Distributed Replay clients work together to simulate workloads against an instance of SQL Server. There can be one or more clients in each Distributed Replay environment.
- Target server: An instance of SQL Server that the Distributed Replay clients can use to replay trace data. We recommend that the target server be located in a test environment.
Next Screen
Next & Next >> Services and Startup Type. Manual | automatically as you wish you can do
Next Screen
Next >>
Next >>
Controller Name :- dbacontroller (as you wish name can be)
Working Dir location: - you can specify where ever you can D drive or C drive
Result Dir location: - you can specify where ever you can D drive or C drive
Installed successfully
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>NET START "SQL Server Distributed Replay Controller"
The SQL Server Distributed Replay Controller service is starting.
The SQL Server Distributed Replay Controller service was started successfully.
C:\Users\Administrator>NET STOP "SQL Server Distributed Replay Controller"
The SQL Server Distributed Replay Controller service is stopping.
The SQL Server Distributed Replay Controller service was stopped successfully.
--------Some More in Next articles
No comments:
Post a Comment