Merge pull request #21725 from markingmyname/issues

[Issue-a-thon - 04/2022] Updates suggested by external contributors

Author: laurabren

docs/azure-data-studio/extensions/media/schema-compare-extension/schema-compare-marketplace-search.png

@@ -8,7 +8,7 @@ author: "yualan"
 ms.author: "alayu"
 ms.reviewer: "maghan"
 ms.custom: 
-ms.date: 11/04/2019
+ms.date: 04/15/2022
 ---
 
 # Schema Compare extension
@@ -36,7 +36,7 @@ It can be tedious to manually manage and synchronize different database versions
 
 1. Select the Extensions Icon to view the available extensions.
 
-    ![extension manager icon](media/add-extensions/extension-manager-icon.png)
+    :::image type="content" source="media/schema-compare-extension/schema-compare-marketplace-search.png" alt-text="marketplace search":::
 
 2. Search for the **Schema Compare** extension and select it to view its details. Select **Install** to add the extension.
 
@@ -46,11 +46,11 @@ It can be tedious to manually manage and synchronize different database versions
 
 1. To open the Schema Compare dialog, **right-click** a database in the Object Explorer and Select **Schema Compare**. The database you select is set as the Source database in the comparison.
 
-    ![schema compare launch menu](media/schema-compare-extension/schema-compare-launch.png)
+    :::image type="content" source="media/schema-compare-extension/schema-compare-launch.png" alt-text="schema compare launch":::
 
 2. Select one of the ellipses (...) to change the Source and Target of your Schema Compare and Select OK.
 
-    ![schema compare select source/target](media/schema-compare-extension/schema-compare-select-source-target.png)
+    :::image type="content" source="media/schema-compare-extension/schema-compare-select-source-target.png" alt-text="schema compare select source target":::
 
 3. To customize your comparison, Select the **Options** button in the toolbar.
 

docs/azure-data-studio/extensions/schema-compare-extension.md

@@ -1,56 +1,57 @@
 ---
 title: View and Analyze Traces
-titleSuffix: SQL Server Profiler
 description: Find out how to use SQL Server Profiler to view trace data, find specific events, display object names, and troubleshoot problems.
 ms.prod: sql
 ms.prod_service: sql-tools
-ms.reviewer: ""
 ms.technology: profiler
 ms.topic: conceptual
-ms.assetid: 17e821ca-a12e-4192-acc1-96765d9ae266
 author: markingmyname
 ms.author: maghan
+ms.reviewer: ""
 ms.custom: seo-lt-2019
 ms.date: 03/14/2017
 ---
 
 # View and Analyze Traces with SQL Server Profiler
 
- [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
+[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-Use [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] to view captured event data in a trace. [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] displays data based on defined trace properties. One way to analyze [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] data is to copy the data to another program, such as [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or [!INCLUDE[ssDE](../../includes/ssde-md.md)] Tuning Advisor. [!INCLUDE[ssDE](../../includes/ssde-md.md)] Tuning Advisor can use a trace file that contains SQL batch and remote procedure call (RPC) events if the **Text** data column is included in the trace. To make sure that the correct events and columns are captured for use with [!INCLUDE[ssDE](../../includes/ssde-md.md)] Tuning Advisor, use the predefined Tuning template that is supplied with [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)].  
+Use SQL Server Profiler to view captured event data in a trace. SQL Server Profiler displays data based on defined trace properties. One way to analyze SQL Server data is to copy the data to another program, such as SQL Server or  Database Engine  Tuning Advisor. Database Engine Tuning Advisor can use a trace file that contains SQL batch and remote procedure call (RPC) events if the **Text** data column is included in the trace. To make sure that the correct events and columns are captured for use with Database Engine Tuning Advisor, use the predefined Tuning template that is supplied with SQL Server Profiler .  
 
- When you open a trace by using [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)], the trace file does not need to have the .trc file extension if the file was created by either [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] or SQL Trace system stored procedures.  
+ When you open a trace by using SQL Server Profiler , the trace file does not need to have the .trc file extension if the file was created by either SQL Server Profiler or SQL Trace system stored procedures.  
 
 > [!NOTE]  
->  [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] can also read SQL Trace .log files and generic SQL script files. When opening a SQL Trace .log file that does not have a .log file extension, such as trace.txt, specify **SQLTrace_Log** as the file format.  
+> SQL Server Profiler can also read SQL Trace .log files and generic SQL script files. When opening a SQL Trace .log file that does not have a .log file extension, such as trace.txt, specify **SQLTrace_Log** as the file format.  
   
- You can configure the [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] date and time display format to assist in trace analysis.  
+ You can configure the SQL Server Profiler date and time display format to assist in trace analysis.  
 
-## Troubleshooting Data  
- Using [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)], you can troubleshoot data by grouping traces or trace files by the **Duration**, **CPU**, **Reads**, or **Writes** data columns. Examples of data you might troubleshoot are queries that perform poorly or that have exceptionally high numbers of logical read operations.  
+## Troubleshooting Data
+
+Using SQL Server Profiler, you can troubleshoot data by grouping traces or trace files by the **Duration**, **CPU**, **Reads**, or **Writes** data columns. Examples of data you might troubleshoot are queries that perform poorly or that have exceptionally high numbers of logical read operations.  
 
  Additional information can be found by saving traces to tables and using [!INCLUDE[tsql](../../includes/tsql-md.md)] to query the event data. For example, to determine which **SQL:BatchCompleted** events had excessive wait time, execute the following:  
 
-```  
+```sql
 SELECT  TextData, Duration, CPU  
 FROM    trace_table_name  
 WHERE   EventClass = 12 -- SQL:BatchCompleted events  
 AND     CPU < (Duration * 1000)  
 ```  
 
 > [!NOTE]  
->  The server reports the duration of an event in microseconds (10^-6 seconds) and the amount of CPU time used by the event in milliseconds (10^-3 seconds). The [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] graphical user interface displays the **Duration** column in milliseconds by default, but when a trace is saved to either a file or a database table, the **Duration** column value is written in microseconds.  
+> The server reports the duration of an event in microseconds (10^-6 seconds) and the amount of CPU time used by the event in milliseconds (10^-3 seconds). The SQL Server Profiler graphical user interface displays the **Duration** column in milliseconds by default, but when a trace is saved to either a file or a database table, the **Duration** column value is written in microseconds. These measurements are for Transact-SQL (T-SQL) queries.
   
-## Displaying Object Names When Viewing Traces  
- If you wish to display the name of an object rather than the object identifier (**Object ID**), you must capture the **Server Name** and **Database ID** data columns along with the **Object Name** data column.  
+## Displaying Object Names When Viewing Traces
+
+If you wish to display the name of an object rather than the object identifier (**Object ID**), you must capture the **Server Name** and **Database ID** data columns along with the **Object Name** data column.  
 
  If you choose to group by the **Object ID** data column, make sure you group by the **Server Name** and **Database ID** data columns first, and then by the **Object ID** data column. Similarly, if you choose to group by the **Index ID** data column, make sure you group by the **Server Name**, **Database ID**, and **Object ID** data columns first, and then by the **Index ID** data columns. You must group in this order because object and index IDs are not unique among servers and databases (and among objects for index IDs).  
 
-## Finding Specific Events Within a Trace  
- To find and group events in a trace, follow these steps:  
+## Finding Specific Events Within a Trace
+
+To find and group events in a trace, follow these steps:  
 
-1.  Create your trace.  
+1. Create your trace.  
 
     -   When defining the trace, capture the **Event Class**, **ClientProcessID**, and **Start Time** data columns in addition to any other data columns you want to capture. For more information, see [Create a Trace &#40;SQL Server Profiler&#41;](../../tools/sql-server-profiler/create-a-trace-sql-server-profiler.md).  
 
@@ -62,7 +63,7 @@ AND     CPU < (Duration * 1000)
 
     -   Open the trace file or table, and expand the node of the desired event class; for example, **Deadlock Chain**. For more information, see [Open a Trace File &#40;SQL Server Profiler&#41;](../../tools/sql-server-profiler/open-a-trace-file-sql-server-profiler.md) or [Open a Trace Table &#40;SQL Server Profiler&#41;](../../tools/sql-server-profiler/open-a-trace-table-sql-server-profiler.md).  
 
-    -   Search through the trace data until you find the events for which you are looking (use the **Find** command on the **Edit** menu of [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] to help you find values in the trace). Note the values in the **ClientProcessID** and **Start Time** data columns of the events you trace.  
+    -   Search through the trace data until you find the events for which you are looking (use the **Find** command on the **Edit** menu of SQL Server Profiler to help you find values in the trace). Note the values in the **ClientProcessID** and **Start Time** data columns of the events you trace.  
 
 3.  Display the events in context.  
 
@@ -72,12 +73,11 @@ AND     CPU < (Duration * 1000)
 
  The same technique can be used to find any grouped events. Once you have found the events you seek, group them by **ClientProcessID**, **ApplicationName**, or another event class to view related activity in chronological order.  
 
-## See Also  
- [View a Saved Trace &#40;Transact-SQL&#41;](../../relational-databases/sql-trace/view-a-saved-trace-transact-sql.md)   
- [sys.fn_trace_getinfo &#40;Transact-SQL&#41;](../../relational-databases/system-functions/sys-fn-trace-getinfo-transact-sql.md)   
- [View Filter Information &#40;SQL Server Profiler&#41;](../../tools/sql-server-profiler/view-filter-information-sql-server-profiler.md)   
- [View Filter Information &#40;Transact-SQL&#41;](../../relational-databases/sql-trace/view-filter-information-transact-sql.md)   
- [Open a Trace File &#40;SQL Server Profiler&#41;](../../tools/sql-server-profiler/open-a-trace-file-sql-server-profiler.md)   
- [Open a Trace Table &#40;SQL Server Profiler&#41;](../../tools/sql-server-profiler/open-a-trace-table-sql-server-profiler.md)  
-  
-  
+## See Also
+
+- [View a Saved Trace &#40;Transact-SQL&#41;](../../relational-databases/sql-trace/view-a-saved-trace-transact-sql.md)
+- [sys.fn_trace_getinfo &#40;Transact-SQL&#41;](../../relational-databases/system-functions/sys-fn-trace-getinfo-transact-sql.md)
+- [View Filter Information &#40;SQL Server Profiler&#41;](../../tools/sql-server-profiler/view-filter-information-sql-server-profiler.md)
+- [View Filter Information &#40;Transact-SQL&#41;](../../relational-databases/sql-trace/view-filter-information-transact-sql.md)
+- [Open a Trace File &#40;SQL Server Profiler&#41;](../../tools/sql-server-profiler/open-a-trace-file-sql-server-profiler.md)
+- [Open a Trace Table &#40;SQL Server Profiler&#41;](../../tools/sql-server-profiler/open-a-trace-table-sql-server-profiler.md)