Documente Academic
Documente Profesional
Documente Cultură
Replay
By: Jonathan Kehayias
https://www.sqlskills.com/blogs/jonathan/installing-and-configuring-sql-server-2012-distributed-
replay/
This blog post is the first in a series of posts that will cover how to install, configure, and use the
new Distributed Replay Utility in SQL Server 2012. The distributed replay utility can be used to
assess the impact of changes and upgrades by replaying workload activity against a test
environment based on a replay trace captured from the current production SQL Server
environment. Prior to SQL Server 2012, two features existed that provided replay capabilities
for performance benchmarking and stress testing SQL Server based on a replay workload; SQL
Server Profiler trace replay and RML Utilities. Unlike these two tools, Distributed Replay is not
limited to replaying events from a single computer, which allows you to drive higher loads
against the test environment to better simulate mission-critical workloads by driving load from
multiple clients concurrently.
This blog post will show how to configure a Distributed Replay Controller, using a dedicated
server named SQL2012-DRU, and two Distributed Replay Clients using dedicated servers
named SQL2012-DRU1 and SQL2012-DRU2. For the purposes of performing an actual replay
using Distributed Replay in another post, a separate server named SQL2012-DB1 with the
Database Engine Services and the AdventureWorks2008R2 database installed on it will be used.
On the Distributed Replay Controller page, click the Add button and search directory services
for the client service account previous created in Active Directory; in this case
SQLSKILLSDEMOS\DRUClientSvcAcct.
On the Distributed Replay Client page, type in the name of the server that you previously
installed the Distributed Replay Controller service on in the Controller Name box.
To add a new firewall rule for the DReplay Client using the Windows Firewall with Advanced
Security snapin, Right-Click on Inbound Rules and click on the New Rule menu
item. Specify Program for the Rule Type and click Next.
On the Program page, click Browse and navigate to C:\Program Files (x86)\Microsoft SQL
Server\110\Tools\DReplayClient and select the DReplayClient.exe executable.
On the Action page select the option Allow the connection and then click Next.
On the Profile page, select the appropriate network profiles/locations for the environment,
generally Domain would be sufficient for most corporate domains, and then click Next.
Finally provide a Name for the rule and click Finish to make the firewall changes.
To setup the firewall rule for the Distributed Replay Controller, follow the same steps but instead
of selecting the DReplayClient folder and DReplayClient.exe application, select the
DReplayController folder and DReplayController.exe application
These rules can also be added using NETSH from the command line using the following
commands:
What you want to see in the DReplay Client Log file is:
What you don’t want to see in the DReplay Client Log file is:
If the client fails to register, and the controller name is correct, you need to verify first that the
firewall rules have been established for the client to allow the appropriate inbound connections
from the controller service and that the firewall rules have been established for the controller to
allow the appropriate inbound connections from the client services. If this all checks out, you
need to go troubleshoot the permissions and setup of the services in the environment, which I’ll
cover in a later post.
Related Posts