Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

James Serra's Blog

James is currently a Senior Business Intelligence Architect/Developer and has over 20 years of IT experience. James started his career as a software developer, then became a DBA 12 years ago, and for the last five years he has been working extensively with Business Intelligence using the SQL Server BI stack (SSAS, SSRS, and SSIS). James has been at times a permanent employee, consultant, contractor, and owner of his own business. All these experiences along with continuous learning has helped James to develop many successful data warehouse and BI projects. James has earned the MCITP Business Developer 2008, MCITP Database Administrator 2008, and MCITP Database Developer 2008, and has a Bachelor of Science degree in Computer Engineering. His blog is at .

SQL Server “Denali”: Distributed Replay

Replaying multiple threads of a captured trace in SQL Profiler is difficult, and you are limited to replaying the workload from a single computer.  Distributed Replay is a new multi-threaded replay utility in Denali that solves this problem by allowing you to spread the workload of a trace against multiple servers.  So you will have one database server (target server) but multiple replay clients executing traces (up to 16 clients with each running up to 255 threads), with a control server (replay controller) coordinating it all.  This allows you to do stress testing for multiple production workload scenarios, such as how an upgrade to a later version of SQL Server will affect your application, or if running on a database server with more physical memory will resolve a performance problem, or if running on a database server with more CPU’s will increase throughput.

There is a configuration file to modify settings, such as how much time to wait after a connection is made until it executes the first transaction (connect time) or how much time to wait between transactions (think time).

So after you have application changes, configuration changes, or upgrades, use Distributed Replay to help protect performance by testing the impact of the changes.

Distributed Replay is installed separately from the regular SQL Server install and all commands are run from the command line.

It has two modes: Synchronization Mode, which runs as your workload would run, using the wait times between commands, and Stress Mode, where there is no waiting so it runs as fast as possible to stress your server

The bottom line is Distributed Replay should make load testing much easier.

More Info:

TechEd Video: What’s New in Manageability for Microsoft SQL Server Code-Named “Denali” (10:22 mark to 28:34)

SQL Server Distributed Replay

Distributed Replay Utility Concepts

Comments

No comments.

Leave a Comment

Please register or log in to leave a comment.