SQL Server Database Experimentation Assistant - How to Run a Capture


Very basic look at the setup as I couldn’t find much documentation on this when I last tried this out in 2018. Maybe it will help you get started a little more quickly. I’ve not had a chance to leverage the actual comparisons across a large workload. When I originally wrote up the basics on this last year I found my needs required more customized load testing approaches.

Added the DRCReplay.exe and the controller services by pulling up the feature setup and adding existing features to existing SQL instance installed.

Add Feature

Pointed the controller directory to a new directory I created

[io.directory]::CreateDirectory('X:\Microsoft SQL Server\DReplayClient\WorkingDir')
[io.directory]::CreateDirectory('X:\Microsoft SQL Server\DReplayClient\ResultDir')

Started with backup of the database before executing the activity I wanted to trace.

dbatools\backup-dbadatabase -sqlinstance localhost -database $Dbname -CopyOnly -CompressBackup

Initialized application application activity, and then recorded in DEA. The result was now in the capture section.

DEA Captures

Restoring after trace was recorded in DEA was simple with the following command from Dbatools

restore-dbadatabase -SqlInstance localhost -Path "<BackupFilePath>" -DatabaseName SMALL -WithReplace

After this restore, initiating the replay was achieved by going to the replay tab.

DEA Replay


(No webmentions yet.)