Skip to content

Commit 4286ddd

Browse files
v-aljev-alje
authored
Merge pull request #3946 from MicrosoftDocs/master
11/14 PM Publish
2 parents 6d7eea7 + 7ddb435 commit 4286ddd

14 files changed

Lines changed: 193 additions & 132 deletions

‎docs/relational-databases/performance/open-view-and-print-a-deadlock-file-sql-server-management-studio.md‎

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Open, View, and Print a Deadlock File (SQL Server Management Studio) | Microsoft Docs"
2+
title: "Open, view, and print a deadlock file (SQL Server Management Studio) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/01/2017"
55
ms.prod: "sql-server-2016"
@@ -21,26 +21,26 @@ ms.author: "jhubbard"
2121
manager: "jhubbard"
2222
ms.workload: "Inactive"
2323
---
24-
# Open, View, and Print a Deadlock File (SQL Server Management Studio)
25-
When [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] generates a deadlock, you can capture and save the deadlock information to a file. After you have saved the deadlock file, you can open it in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] to view or print.
24+
# Open, view, and print a deadlock file (SQL Server Management Studio)
25+
When [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] generates a deadlock, you can capture and save the deadlock information to a file. After you've saved the deadlock file, you can open it in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] to view it or print it.
2626

27-
### To open and view a deadlock file
27+
## Open and view a deadlock file
2828

29-
1. On the **File** menu in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)], point to **Open**, and then click **File**.
29+
1. On the **File** menu in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)], point to **Open**, and then select **File**.
3030

31-
2. In the **Open File** dialog box, select the .xdl file type in the **Files of type** box. You will now have a filtered list of only deadlock files.
31+
2. In the **Open File** dialog box, select the .xdl file type in the **Files of type** box. You now have a filtered list of only deadlock files.
3232

33-
### To print a deadlock file
33+
## Print a deadlock file
3434

35-
1. On the **File** menu in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)], point to **Open,** and then click **File**.
35+
1. On the **File** menu in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)], point to **Open**, and then select **File**.
3636

37-
2. In the **Open File** dialog box, select the .xdl file type in the **Files of type** box. You will now have a filtered list of only deadlock files.
37+
2. In the **Open File** dialog box, select the .xdl file type in the **Files of type** box. You now have a filtered list of only deadlock files.
3838

39-
3. Select the deadlock file you want to print, and click **Open**.
39+
3. Select the deadlock file you want to print, and select **Open**.
4040

41-
4. On the **File** menu, click **Print.**
41+
4. On the **File** menu, select **Print**.
4242

43-
## See Also
44-
[Save Deadlock Graphs (SQL Server Profiler)](../../relational-databases/performance/save-deadlock-graphs-sql-server-profiler.md)
43+
## See also
44+
[Save deadlock graphs (SQL Server Profiler)](../../relational-databases/performance/save-deadlock-graphs-sql-server-profiler.md)
4545

4646

‎docs/relational-databases/performance/save-deadlock-graphs-sql-server-profiler.md‎

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Save Deadlock Graphs (SQL Server Profiler) | Microsoft Docs"
2+
title: "Save deadlock graphs (SQL Server Profiler) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/01/2017"
55
ms.prod: "sql-server-2016"
@@ -20,49 +20,49 @@ ms.author: "jhubbard"
2020
manager: "jhubbard"
2121
ms.workload: "On Demand"
2222
---
23-
# Save Deadlock Graphs (SQL Server Profiler)
23+
# Save deadlock graphs (SQL Server Profiler)
2424
This topic describes how to save a deadlock graph by using [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)]. Deadlock graphs are saved as XML files.
2525

26-
### To save deadlock graph events separately
26+
## Save deadlock graph events separately
2727

28-
1. On the **File** menu, click **New Trace**, and then connect to an instance of SQL Server.
28+
1. On the **File** menu, select **New Trace**, and then connect to an instance of SQL Server.
2929

30-
The **Trace Properties**dialog box appears.
30+
The **Trace Properties** dialog box appears.
3131

3232
> [!NOTE]
33-
> If **Start tracing immediately after making connection** is selected, the **Trace Properties**dialog box fails to appear, and the trace begins instead. To turn off this setting, on the **Tools**menu, click **Options**, and clear the **Start tracing immediately after making connection** check box.
33+
> If you select **Start tracing immediately after making connection**, the **Trace Properties** dialog box fails to appear, and the trace begins instead. To turn off this setting, on the **Tools** menu, select **Options**, and clear the **Start tracing immediately after making connection** check box.
3434
35-
2. In the Trace Properties dialog box, type a name for the trace in the**Trace name** box.
35+
2. In the **Trace Properties** dialog box, type a name for the trace in the **Trace name** box.
3636

37-
3. In the **Use the template** list, select a trace template on which to base the trace, or select **Blank** if you do not want to use a template.
37+
3. In the **Use the template** list, select a trace template on which to base the trace. If you don't want to use a template, select **Blank**.
3838

39-
4. Do one of the following:
39+
4. Do one of the following:
4040

41-
- Select the**Save to file** check box to capture the trace to a file. Specify a value for **Set maximum file size**.
41+
- To capture the trace to a file, select the **Save to file** check box. Specify a value for **Set maximum file size**.
4242

43-
Optionally, select **Enable file rollover** and **Server processes trace data**.
43+
Optionally, select the **Enable file rollover** and **Server processes trace data** check boxes.
4444

45-
- Select the **Save to table** check box to capture the trace to a database table.
45+
- To capture the trace to a database table, select the **Save to table** check box.
4646

47-
Optionally, click **Set maximum rows**, and specify a value.
47+
Optionally, select **Set maximum rows**, and specify a value.
4848

49-
5. Optionally, select the **Enable trace stop time** check box, and specify a stop date and time.
49+
5. Optionally, select the **Enable trace stop time** check box, and specify a stop date and time.
5050

51-
6. Click the **Events Selection**tab.
51+
6. Select the **Events Selection** tab.
5252

53-
7. In the **Events**data column, expand the **Locks**event category, and then select the **Deadlock graph**check box. If the Locks event category is not available, check **Show all events** to display it.
53+
7. In the **Events** data column, expand the **Locks** event category, and then select the **Deadlock graph** check box. If the **Locks** event category isn't available, select the **Show all events** check box to display it.
5454

55-
The **Events Extraction Settings**tab is added to the **Trace Properties**dialog box.
55+
The **Events Extraction Settings** tab is added to the **Trace Properties** dialog box.
5656

57-
8. On the **Events Extraction Settings**tab, click **Save Deadlock XML Events Separately**.
57+
8. On the **Events Extraction Settings** tab, select **Save Deadlock XML Events Separately**.
5858

59-
9. In the **Save As** dialog box, enter the name of the file in which to store the deadlock graph events.
59+
9. In the **Save As** dialog box, enter the name of the file where you want to store the deadlock graph events.
6060

61-
10. Click **All Deadlock XML batches in a single file** to save all deadlock graph events in a single XML file, or click **Each Deadlock XML batch in a distinct file**to create a new XML file for each deadlock graph.
61+
10. Select **All Deadlock XML batches in a single file** to save all deadlock graph events in a single XML file. Or select **Each Deadlock XML batch in a distinct file** to create a new XML file for each deadlock graph.
6262

63-
After you have saved the deadlock file, you can open the file in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)]. For more information, see [Open, View, and Print a Deadlock File (SQL Server Management Studio)](../../relational-databases/performance/open-view-and-print-a-deadlock-file-sql-server-management-studio.md).
63+
After you save the deadlock file, you can open the file in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)]. For more information, see [Open, view, and print a deadlock file (SQL Server Management Studio)](../../relational-databases/performance/open-view-and-print-a-deadlock-file-sql-server-management-studio.md).
6464

65-
## See Also
66-
[Analyze Deadlocks with SQL Server Profiler](../../tools/sql-server-profiler/analyze-deadlocks-with-sql-server-profiler.md)
65+
## See also
66+
[Analyze deadlocks with SQL Server Profiler](../../tools/sql-server-profiler/analyze-deadlocks-with-sql-server-profiler.md)
6767

6868

‎docs/relational-databases/performance/save-showplan-xml-events-separately-sql-server-profiler.md‎

Lines changed: 25 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Save Showplan XML Events Separately (SQL Server Profiler) | Microsoft Docs"
2+
title: "Save Showplan XML events separately (SQL Server Profiler) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/01/2017"
55
ms.prod: "sql-server-2016"
@@ -20,45 +20,49 @@ ms.author: "jhubbard"
2020
manager: "jhubbard"
2121
ms.workload: "Inactive"
2222
---
23-
# Save Showplan XML Events Separately (SQL Server Profiler)
24-
This topic describes how to save **Showplan XML** events that are captured in traces into separate .SQLPlan files by using [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)]. You can open the **Showplan XML** event files in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)], which enables you to view the graphical execution plan for each event.
23+
# Save Showplan XML events separately (SQL Server Profiler)
24+
This topic describes how to save **Showplan XML** events that are captured in traces into separate .SQLPlan files by using [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)]. You can open the **Showplan XML** event files in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] so that you can view the graphical execution plan for each event.
2525

26-
### To save Showplan XML events separately
26+
## Save Showplan XML events separately
2727

28-
1. On the **File** menu, click **New Trace**, and then connect to an instance of SQL Server.
28+
1. On the **File** menu, select **New Trace**, and then connect to an instance of SQL Server.
2929

30-
The **Trace Properties**dialog box appears.
30+
The **Trace Properties** dialog box appears.
3131

3232
> [!NOTE]
33-
> If **Start tracing immediately after making connection**is selected, the **Trace Properties**dialog box fails to appear and the trace begins instead. To turn off this setting, on the **Tools**menu, click **Options**, and clear the **Start tracing immediately after making connection** check box.
33+
> If you select **Start tracing immediately after making connection**, the **Trace Properties** dialog box fails to appear, and the trace begins instead. To turn off this setting, on the **Tools** menu, select **Options**, and clear the **Start tracing immediately after making connection** check box.
3434
35-
2. In the **Trace Properties** dialog box, type a name for the trace in the **Trace name** box.
35+
2. In the **Trace Properties** dialog box, type a name for the trace in the **Trace name** box.
3636

37-
3. In the **Use the template** list, select a trace template on which to base the trace, or select **Blank** if you do not want to use a template.
37+
3. In the **Use the template** list, select a trace template on which to base the trace. If you don't want to use a template, select **Blank**.
3838

39-
4. Do one of the following:
39+
4. Do one of the following:
4040

41-
- Select the**Save to file** check box to capture the trace to a file. Specify a value for **Set maximum file size**. Optionally, select the **Enable file rollover** and **Server processes trace data** check boxes.
41+
- To capture the trace to a file, select the **Save to file** check box. Specify a value for **Set maximum file size**.
42+
43+
Optionally, select the **Enable file rollover** and **Server processes trace data** check boxes.
4244

43-
- Select the**Save to table** check box to capture the trace to a database table. Optionally click **Set maximum rows**, and specify a value.
45+
- To capture the trace to a database table, select the **Save to table** check box.
46+
47+
Optionally, select **Set maximum rows**, and specify a value.
4448

45-
5. Optionally, select the **Enable trace stop time** check box, and specify a stop date and time.
49+
5. Optionally, select the **Enable trace stop time** check box, and specify a stop date and time.
4650

47-
6. Click the **Events Selection**tab.
51+
6. Select the **Events Selection** tab.
4852

49-
7. In the **Events**data column, expand the **Performance**event category, and then select the **Showplan XML**check box. If the **Performance** event category is not available, check **Show all events** to display it.
53+
7. In the **Events** data column, expand the **Performance** event category, and then select the **Showplan XML** check box. If the **Performance** event category is not available, select **Show all events** to display it.
5054

51-
The **Events Extraction Settings**tab is added to the **Trace Properties**dialog box.
55+
The **Events Extraction Settings** tab is added to the **Trace Properties** dialog box.
5256

53-
8. On the **Events Extraction Settings**tab, click **Save XML Showplan events separately**.
57+
8. On the **Events Extraction Settings** tab, select **Save XML Showplan events separately**.
5458

5559
9. In the **Save As** dialog box, enter the name of the file in which to store the **Showplan XML** events.
5660

57-
10. Click **All XML Showplan batches in a single file** to save all **Showplan XML** events in a single XML file, or click **Each XML Showplan batch in a distinct file**to create a new XML file for each **Showplan XML** event.
61+
10. Select **All XML Showplan batches in a single file** to save all **Showplan XML** events in a single XML file. Or select **Each XML Showplan batch in a distinct file** to create a new XML file for each **Showplan XML** event.
5862

59-
11. To view the **Showplan XML** event file in SQL Server Management Studio, on the **File** menu, point to **Open**, and click **File**. Navigate to the directory where you saved the **Showplan XML** event file or files to select one and open it. **Showplan XML** event files have a .SQLPlan file extension.
63+
11. To view the **Showplan XML** event file in SQL Server Management Studio, on the **File** menu, point to **Open**, and select **File**. Browse to the directory where you saved the **Showplan XML** event file or files to select one and open it. **Showplan XML** event files have a .SQLPlan file extension.
6064

61-
## See Also
62-
[Analyze Queries with SHOWPLAN Results in SQL Server Profiler](../../tools/sql-server-profiler/analyze-queries-with-showplan-results-in-sql-server-profiler.md)
65+
## See also
66+
[Analyze queries with Showplan results in SQL Server Profiler](../../tools/sql-server-profiler/analyze-queries-with-showplan-results-in-sql-server-profiler.md)
6367

6468

0 commit comments

Comments
 (0)