You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/database-engine/availability-groups/windows/secondary-replica-connection-redirection-always-on-availability-groups.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ The preceding table shows that when the primary replica has `READ_WRITE_ROUTING_
78
78
In this example, an availability group has three replicas:
79
79
* A primary replica on COMPUTER01
80
80
* A synchronous secondary replica on COMPUTER02
81
-
* A synchronous secondary replica on COMPUTER03
81
+
* A asynchronous secondary replica on COMPUTER03
82
82
83
83
The following picture represents the availability group.
84
84
@@ -118,7 +118,7 @@ CREATE AVAILABILITY GROUP MyAg
Copy file name to clipboardExpand all lines: docs/dea/database-experimentation-assistant-capture-trace.md
+32-19Lines changed: 32 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Capture a trace for SQL Server upgrades
3
3
description: Capture a trace in Database Experimentation Assistant for SQL Server upgrades
4
4
ms.custom: "seo-lt-2019"
5
-
ms.date: 11/21/2019
5
+
ms.date: 12/05/2019
6
6
ms.prod: sql
7
7
ms.prod_service: dea
8
8
ms.suite: sql
@@ -22,46 +22,59 @@ Before you start a trace capture, make sure that you back up all target database
22
22
23
23
Query caching in SQL Server might affect evaluation results. We recommend that you restart the SQL Server service (MSSQLSERVER) in the services application to improve the consistency of evaluation results.
24
24
25
-
## Create a trace capture
25
+
## Configure a trace capture
26
26
27
-
1. In DEA, select the menu icon in the left menu. In the expanded menu, select **Capture Traces**next to the camera icon.
27
+
1. In DEA, on the left-hand navigation bar, select the camera icon, and then on the **All Captures**page, select **New Capture**.
28
28
29
-
29
+
30
30
31
-
2. Under **New Capture**, enter or select the following information:
31
+
2. On the **New Capture** page, under **Capture details**, enter or select the following information:
32
+
33
+
-**Capture name**: Enter a name for the trace file for your capture.
34
+
-**Format**: Specify the format (Trace or XEvents) for the capture.
35
+
-**Duration**: Select the length of time (in minutes) that you want the trace capture to run.
36
+
-**Capture Location**: Select the destination path for the trace file.
32
37
33
-
-**SQL Server instance name**: Enter a name for the computer running SQL Server on which you want to capture a server trace.
34
-
-**Database name**: Enter a name for a database on which to start a database trace. If you don't specify a database, trace is captured on all the databases on the server.
35
-
-**Trace file name**: Enter a name for the trace file for your capture.
36
-
-**Max file size (MB)**: Select the rollover size for files. A new file is created as needed at the file size you select. The recommended rollover size is 200 MB.
37
-
-**Duration (in min)**: Select the length of time (in minutes) that you want the trace capture to run.
38
-
-**Path to store output trace file**: Select the destination path for the trace file.
39
38
40
39
> [!NOTE]
41
40
> The file path to the trace file must be on the computer that's running SQL Server. If the SQL Server service isn't set for a specific account, the service might need write permissions to the specified folder for the trace file to be written.
Also be sure to select the **Yes, I have manually taken the backup…** check box.
43
+
44
+
3. Under **Capture details**, enter or select the following information:
45
+
46
+
-**Server Type**: Specify the type of the SQL server (**SqlServer**, **AzureSqlDb**, **AzureSqlManagedInstance**).
47
+
-**Server name**: Specify the server name or IP address of your SQL Server.
48
+
-**Authentication Type**: For the authentication type, select **Windows**.
49
+
-**Database name**: Enter a name for a database on which to start a database trace. If you don't specify a database, trace is captured on all the databases on the server.
50
+
51
+
Also be sure to select or deselect the **Encrypt connection** and **Trust server certificate** check boxes as appropriate for your scenario.
After you enter or select the required information, select **Start** to initiate the trace capture. If the information you've provided on the **New Capture** page is valid, the trace capture process begins without issue. Otherwise, text boxes with invalid entries are highlighted with red. Provide corrected information, and then try again.
57
+
1. After you enter or select the required information, select **Start** to initiate the trace capture.
58
+
59
+
If the information you entered is valid, the trace capture process begins. Otherwise, text boxes with invalid entries are highlighted in red. If you do encounter errors, correct any necessary entries, and then select **Start** again.
60
+
61
+
While the trace capture is running, under **Capture details**, the status and progress of the trace capture process is displayed.
49
62
50
-
Select the bell icon at the bottom of the left menu to monitor the progress of the capture.
2. When the tracecapture is finished running, the new trace (.trc) file is saved in the **Capture location** you specific during initial configuration.
When the trace capture finishes running, a .trc file is written in the location specified in the **Path to store output trace file** field. The trace file includes trace results of the activity of a SQL Server database. .trc files are designed to provide more information about errors that are detected and reported by SQL Server.
69
+
The trace file includes trace results of the activity of a SQL Server database. .trc files are designed to provide more information about errors that are detected and reported by SQL Server.
57
70
58
71
## Frequently asked questions about trace capture
59
72
60
73
Following are some frequently asked questions about trace capture in DEA.
61
74
62
75
**Q: What events are captured when I run a trace capture on a production database?**
63
76
64
-
The following table provides the list of events and the corresponding column data that we collect for traces:
77
+
The following table lists the events and corresponding column data that DEA collects for traces:
65
78
66
79
|Event Name|Text Data (1)|Binary Data (2)|Database ID (3)|Host Name (8)|Application Name (10)|Login Name (11)|SPID (12)|Start Time (14)|End Time (15)|Database Name (35)|Event Sequence (51)|IsSystem (60)|
0 commit comments