Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Distributed Replay
By Stéphane Savorgnano March 28, 2013 Database management No Comments
https://blog.dbi-services.com/sql-server-2012-installing-and-configuring-distributed-replay/
Distributed Replay is a new fonctionality of Microsoft SQL Server 2012. It helps you assess the
impact of future upgrades (SQL Server, hardware, OS) or SQL Server tunings by replaying a
trace captured from a productive SQL Server environment to a new SQL Server test
environment.
This new functionality is similar to SQL Server Profiler, but with more possibilities: e. g.
replaying the trace from multiple clients (up to sixteen), use a stress or synchronization mode,
configure options like think time, or connect time etc.
Do not fortget to also install Management Tools which provides Distributed Replay
administration tools!
First, we have to create two Active Directory accounts.
We now have to install Distributed Replay Controller, Distributed Replay Client, and
Management Tools on our VMTESTSQLWIN01 server which will be the Controller of our
Distributed Replay and also the Client:
On the Server Configuration, add the two Actice Directory accounts created for Distributed
Replay Controller and Distributed Replay Client:
On the Distributed Replay Controller Page, add the Active Directory account previously created
for the Controller. On the Distributed Replay Client page, add the Controller name:
On the Server Configuration, add the Actice Directory account created for Distributed Replay
Client:
Configure the Distributed Replay Controller for the client:
To allow Distributed Replay Clients to connect and register to the Distributed Replay controller,
inbound connection for DReplayClient.exe application has to be allowed on each Distributed
Replay Client through the Windows firewall.
Go to Windows firewall, Inbound Rules, and add a new rule for a program:
Browse to the DReplayClient.exe location:
In the target Server VMTESTSQLWIN03, we also have to configure the Windows firewall for
inbound on port TCP 1433 to let the Distributed Replay Client write on the target. Select the
port:
Specify a name for this new inbound and click Finish to save it:
Now the firewall is configured on each server!
You first have to start the Controller service on the Distributed Replay Controller.
Go to VMTESTSQLWIN01, open a command prompt screen and enter:
You should see the result of this command in the log folder of Distributed Replay Controller
under C:Program Files (x86)Microsoft SQL Server110ToolsDReplayControllerlog.
You have now to start Distributed Replay Client service on your Distributed Replay Clients
VMTESTSQLWIN01 and VMTESTSQLWIN02. Verify that they are correctly synchronised
with your Distributed Replay Controller.
If this was successul for the two clients, the configuration between the controller and clients is
finished and the Distributed Replay is ready to work.
Conclusion
At this point, our Distributed Replay application is ready to use, clients and controller are
registred together.
You now have to create a trace, preprocess it and replay it from our clients to the target SQL
Server.