Skip to content

Commit 0feee1f

Browse files
markingmynamemarkingmyname
committed
[Dist Replay] fixed broken links from OPS site
1 parent 3269212 commit 0feee1f

3 files changed

Lines changed: 70 additions & 72 deletions

File tree

‎docs/tools/distributed-replay/install-distributed-replay-overview.md‎

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,6 @@ Use the following topics to install the Distributed Replay feature.
2727
|[Complete the Post-Installation Steps](../../tools/distributed-replay/complete-the-post-installation-steps.md)|Procedural topic for completing a Distributed Replay installation.|
2828
|[Modify the Controller and Client Services Accounts](../../tools/distributed-replay/modify-the-controller-and-client-services-accounts.md)|Procedural topic for how to start and stop the Distributed Replay controller and client services, and modify the service accounts.|
2929

30-
## See Also
31-
[Install SQL Server 2016](../../database-engine/install-windows/install-sql-server.md)
32-
33-
30+
## See Also
31+
32+
-[Install SQL Server 2016](../../database-engine/install-windows/install-sql-server.md)

‎docs/tools/distributed-replay/install-distributed-replay.md‎

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -205,18 +205,17 @@ setup /q /ACTION=/proxy/https/github.com/MicrosoftDocs/sql-docs/commit/Install /FEATURES=DREPLAY_CLT /IAcceptSQLServerLicenseTerms /CL
205205

206206
Following is an example on how to specify the configuration file at the command prompt:
207207

208-
```
208+
```
209209
Setup.exe /CTLRSVCPASSWORD="ctlrsvcpswd" /CLTSVCPASSWORD="cltsvcpswd" / ConfigurationFile=ConfigurationFile.INI\
210-
```
211-
212-
> [!NOTE]
213-
> You must specify both passwords in the command line because you cannot configure them in the configuration file.
214-
215-
## See Also
216-
[Features Supported by the Editions of SQL Server 2016](~/sql-server/editions-and-supported-features-for-sql-server-2016.md)
217-
[SQL Server Distributed Replay](../../tools/distributed-replay/sql-server-distributed-replay.md)
218-
[Distributed Replay Requirements](../../tools/distributed-replay/distributed-replay-requirements.md)
219-
[Administration Tool Command-line Options (Distributed Replay Utility)](../../tools/distributed-replay/administration-tool-command-line-options-distributed-replay-utility.md)
220-
[Configure Distributed Replay](../../tools/distributed-replay/configure-distributed-replay.md)
221-
222-
210+
```
211+
212+
> [!NOTE]
213+
> You must specify both passwords in the command line because you cannot configure them in the configuration file.
214+
215+
## See Also
216+
217+
- [Features Supported by the Editions of SQL Server 2016](~/sql-server/editions-and-supported-features-for-sql-server-2016.md)
218+
- [SQL Server Distributed Replay](../../tools/distributed-replay/sql-server-distributed-replay.md)
219+
- [Distributed Replay Requirements](../../tools/distributed-replay/distributed-replay-requirements.md)
220+
- [Administration Tool Command-line Options (Distributed Replay Utility)](../../tools/distributed-replay/administration-tool-command-line-options-distributed-replay-utility.md)
221+
- [Configure Distributed Replay](../../tools/distributed-replay/configure-distributed-replay.md)

‎docs/tools/distributed-replay/sql-server-distributed-replay.md‎

Lines changed: 54 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ ms.topic: conceptual
77
ms.assetid: 58ef7016-b105-42c2-90a0-364f411849a4
88
author: markingmyname
99
ms.author: maghan
10+
ms.reviewer: mikeray
1011
ms.custom: seo-lt-2019
1112
ms.date: 03/14/2017
1213
---
@@ -15,59 +16,58 @@ ms.date: 03/14/2017
1516

1617
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
1718

18-
The [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributed Replay feature helps you assess the impact of future [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] upgrades. You can also use it to help assess the impact of hardware and operating system upgrades, and [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] tuning.
19-
20-
## Benefits of Distributed Replay
21-
Similar to [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)], you can use Distributed Replay to replay a captured trace against an upgraded test environment. Unlike [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)], Distributed Replay is not limited to replaying the workload from a single computer.
22-
23-
Distributed Replay offers a more scalable solution than [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)]. With Distributed Replay, you can replay a workload from multiple computers and better simulate a mission-critical workload.
24-
25-
The [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributed Replay feature can use multiple computers to replay trace data and simulate a mission-critical workload. Use Distributed Replay for application compatibility testing, performance testing, or capacity planning.
26-
27-
## When to Use Distributed Replay
28-
[!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] and Distributed Replay provide some overlap in functionality.
29-
30-
You may use [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] to replay a captured trace against an upgraded test environment. You can also analyze the replay results to look for potential functional and performance incompatibilities. However, [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] can only replay a workload from a single computer. When replaying an intensive OLTP application that has many active concurrent connections or high throughput, [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] can become a resource bottleneck.
31-
32-
Distributed Replay offers a more scalable solution than [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)]. Use Distributed Replay to replay a workload from multiple computers and better simulate a mission-critical workload.
33-
34-
The following table describes when to use each tool.
35-
36-
|Tool|Use When...|
37-
|----------|---------------|
38-
|[!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)]|You want to use the conventional replay mechanism on a single computer. In particular, you need line-by-line debugging capabilities, such as the **Step**, **Run to Cursor**, and **Toggle Breakpoint** commands.<br /><br /> You want to replay an [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] trace.|
39-
|Distributed Replay|You want to evaluate application compatibility. For example, you want to test [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and operating system upgrade scenarios, hardware upgrades, or index tuning.<br /><br /> The concurrency in the captured trace is so high that a single replay client cannot sufficiently simulate it.|
40-
41-
## Distributed Replay Concepts
42-
The following components make up the Distributed Replay environment:
43-
44-
- **Distributed Replay administration tool**: A console application, **DReplay.exe**, used to communicate with the distributed replay controller. Use the administration tool to control the distributed replay.
45-
46-
- **Distributed Replay controller**: A computer running the Windows service named [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributed Replay controller. The Distributed Replay controller orchestrates the actions of the distributed replay clients. There can only be one controller instance in each Distributed Replay environment.
47-
48-
- **Distributed Replay clients**: One or more computers (physical or virtual) running the Windows service named [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributed Replay client. The Distributed Replay clients work together to simulate workloads against an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. There can be one or more clients in each Distributed Replay environment.
49-
50-
- **Target server**: An instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that the Distributed Replay clients can use to replay trace data. We recommend that the target server be located in a test environment.
51-
52-
The Distributed Replay administration tool, controller, and client can be installed on different computers or the same computer. There can be only one instance of the Distributed Replay controller or client service that is running on the same computer.
53-
54-
The following figure shows the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributed Replay physical architecture:
55-
56-
![Distributed Replay Architecture](../../tools/distributed-replay/media/distributedreplayarch.gif "Distributed Replay Architecture")
57-
58-
## Distributed Replay Tasks
59-
19+
The [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributed Replay feature helps you assess the impact of future [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] upgrades. You can also use it to help assess the impact of hardware and operating system upgrades, and [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] tuning.
20+
21+
## Benefits of Distributed Replay
22+
23+
Similar to SQL Server Profiler, you can use Distributed Replay to replay a captured trace against an upgraded test environment. Unlike SQL Server Profiler, Distributed Replay is not limited to replaying the workload from a single computer.
24+
25+
Distributed Replay offers a more scalable solution than SQL Server Profiler. With Distributed Replay, you can replay a workload from multiple computers and better simulate a mission-critical workload.
26+
27+
The [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributed Replay feature can use multiple computers to replay trace data and simulate a mission-critical workload. Use Distributed Replay for application compatibility testing, performance testing, or capacity planning.
28+
29+
## When to Use Distributed Replay
30+
31+
SQL Server Profiler and Distributed Replay provide some overlap in functionality.
32+
33+
You may use SQL Server Profiler to replay a captured trace against an upgraded test environment. You can also analyze the replay results to look for potential functional and performance incompatibilities. However, SQL Server Profiler can only replay a workload from a single computer. When replaying an intensive OLTP application that has many active concurrent connections or high throughput, SQL Server Profiler can become a resource bottleneck.
34+
35+
Distributed Replay offers a more scalable solution than SQL Server Profiler. Use Distributed Replay to replay a workload from multiple computers and better simulate a mission-critical workload.
36+
37+
The following table describes when to use each tool.
38+
39+
|Tool|Use When...|
40+
|----------|---------------|
41+
| SQL Server Profiler | You want to use the conventional replay mechanism on a single computer. In particular, you need line-by-line debugging capabilities, such as the **Step**, **Run to Cursor**, and **Toggle Breakpoint** commands.<br /><br /> You want to replay an [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] trace. |
42+
| Distributed Replay |You want to evaluate application compatibility. For example, you want to test [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and operating system upgrade scenarios, hardware upgrades, or index tuning.<br /><br /> The concurrency in the captured trace is so high that a single replay client can't sufficiently simulate it.|
43+
44+
## Distributed Replay Concepts
45+
46+
The following components make up the Distributed Replay environment:
47+
48+
- **Distributed Replay administration tool**: A console application, **DReplay.exe**, used to communicate with the distributed replay controller. Use the administration tool to control the distributed replay.
49+
50+
- **Distributed Replay controller**: A computer running the Windows service named [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributed Replay controller. The Distributed Replay controller orchestrates the actions of the distributed replay clients. There can only be one controller instance in each Distributed Replay environment.
51+
52+
- **Distributed Replay clients**: One or more computers (physical or virtual) running the Windows service named [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributed Replay client. The Distributed Replay clients work together to simulate workloads against an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. There can be one or more clients in each Distributed Replay environment.
53+
54+
- **Target server**: An instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that the Distributed Replay clients can use to replay trace data. We recommend that the target server is located in a test environment.
55+
56+
The Distributed Replay administration tool, controller, and client can be installed on different computers or the same computer. There can be only one instance of the Distributed Replay controller or client service that is running on the same computer.
57+
58+
The following figure shows the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Distributed Replay physical architecture:
59+
60+
![Distributed Replay Architecture](../../tools/distributed-replay/media/distributedreplayarch.gif "Distributed Replay Architecture")
61+
62+
## Distributed Replay Tasks
63+
6064
|Task Description|Topic|
6165
|----------------------|-----------|
62-
|Describes how to configure Distributed Replay.|[Configure Distributed Replay](../../tools/distributed-replay/configure-distributed-replay.md)|
63-
|Describes how to prepare the input trace data.|[Prepare the Input Trace Data](../../tools/distributed-replay/prepare-the-input-trace-data.md)|
64-
|Describes how to replay trace data.|[Replay Trace Data](../../tools/distributed-replay/replay-trace-data.md)|
65-
|Describes how to review the Distributed Replay trace data results.|[Review the Replay Results](../../tools/distributed-replay/review-the-replay-results.md)|
66-
|Describes how to use the administration tool to initiate, monitor, and cancel operations on the controller.|[Administration Tool Command-line Options &#40;Distributed Replay Utility&#41;](../../tools/distributed-replay/administration-tool-command-line-options-distributed-replay-utility.md)|
67-
68-
## See Also
69-
[SQL Server Distributed Replay Forum](https://social.technet.microsoft.com/Forums/sl/sqldru/)
70-
[Using Distributed Replay to Load Test Your SQL Server - Part 2](https://blogs.msdn.com/b/mspfe/archive/2012/11/14/using-distributed-replay-to-load-test-your-sql-server-part-2.aspx)
71-
[Using Distributed Replay to Load Test Your SQL Server - Part 1](https://blogs.msdn.com/b/mspfe/archive/2012/11/08/using-distributed-replay-to-load-test-your-sql-server-part-1.aspx)
72-
73-
66+
| Describes how to configure Distributed Replay. | [Configure Distributed Replay](../../tools/distributed-replay/configure-distributed-replay.md) |
67+
| Describes how to prepare the input trace data. | [Prepare the Input Trace Data](../../tools/distributed-replay/prepare-the-input-trace-data.md) |
68+
| Describes how to replay trace data. |[Replay Trace Data](../../tools/distributed-replay/replay-trace-data.md) | | Describes how to review the Distributed Replay trace data results. |[Review the Replay Results](../../tools/distributed-replay/review-the-replay-results.md)|
69+
| Describes how to use the administration tool to initiate, monitor, and cancel operations on the controller. | [Administration Tool Command-line Options &#40;Distributed Replay Utility&#41;](../../tools/distributed-replay/administration-tool-command-line-options-distributed-replay-utility.md) |
70+
71+
## See Also
72+
73+
[SQL Server Distributed Replay Forum](https://social.technet.microsoft.com/Forums/sl/sqldru/)

0 commit comments

Comments
 (0)