You can monitor the process as necessary. Make sure that the values you entered are correct, and then select Start. Otherwise, the text boxes that have incorrect information are highlighted with red. If the information you entered is valid, the Distributed Replay process starts. Select or deselect the Encrypt connection and Trust server certificate check boxes as appropriate for your scenario.Īfter you enter or select the required information, select Start to initiate the trace replay. If you don't specify a database, trace is captured on all the databases on the server.
Database name: Enter a name for a database on which to start a server-side trace.Authentication Type: For the authentication type, select Windows.Server name: Specify the server name or IP address of your SQL Server.Server Type: Specify the type of the SQL server ( SqlServer, AzureSqlDb, AzureSqlManagedInstance).Under SQL Server connection details, enter or select the following information: Verify that you have restored the database(s) by selecting the Yes, I have manually restored the database(s) check box. Replay Trace Location: Specify the path to store trace files/XEvents associated with the trace replay.įor an Azure SQL Database or an Azure SQL Managed Instance, you need to provide the SAS URI of the Azure blob storage account. Replay Tool: Specify the replay tool (DReplay or InBuilt).Ĭontroller machine name: Specify the name of the computer serving as the Distributed Replay Controller. If using DReplay, the file must exist on the computer serving as the DReplay Controller and the user account requires access to the file and folder.
Source Trace Format: Specify the format (Trace or XEvents) of the source trace file.įull path to source file: Specify the full path to the source trace file. Replay name: Enter a name for the trace replay. On the New Replay page, under Replay details, enter or select the following information: The Distributed Replay controller computer requires permissions to the user account that you use to remotely connect. In DEA, on the left-hand navigation bar, select the arrow icon, and then on the All Replays page, select New Replay. Configure a trace replay for target 1įirst, you need to perform a trace replay against target 1, which represents your existing production environment. For more information, see Configure Distributed Replay for Database Experimentation Assistant. Replaying a trace requires that you manually set up virtual machines or physical computers to run Distributed Replay traces.
The trace file for the workload must be replayed twice: one time on an environment with the same version of SQL Server that runs in production and a second time on an environment that has the upgrade target SQL Server version, such as SQL Server 2016. For example, consider a production workload that runs on SQL Server 2008 R2.
In Database Experimentation Assistant (DEA), you can replay a captured trace file against an upgraded test environment. Replay a trace in Database Experimentation Assistant