Refresh some trace filtering articles (UUF 270785)

Author: rwestMSFT

docs/relational-databases/sql-trace/filter-a-trace.md

@@ -1,33 +1,35 @@
 ---
-title: "Set a Trace Filter (Transact-SQL)"
-description: "Set a Trace Filter (Transact-SQL)"
+title: "Set a trace filter (Transact-SQL)"
+description: Learn how to use stored procedures to create a filter that retrieves only the information you need on an event being traced.
 author: "MashaMSFT"
 ms.author: "mathoma"
-ms.date: "03/06/2017"
+ms.reviewer: randolphwest
+ms.date: 07/17/2024
 ms.service: sql
 ms.topic: conceptual
 helpviewer_keywords:
   - "filters [SQL Server], traces"
   - "traces [SQL Server], filters"
 ---
-# Set a Trace Filter (Transact-SQL)
- [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
-  This topic describes how to use stored procedures to create a filter that retrieves only the information you need on an event being traced.  
-  
-### To set a trace filter  
-  
-1.  If the trace is already running, execute **sp_trace_setstatus** by specifying `@status = 0` to stop the trace.  
-  
-2.  Execute **sp_trace_setfilter** to configure the type of information to retrieve for the event being traced.  
+# Set a trace filter (Transact-SQL)
+
+[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
+
+This article describes how to use stored procedures to create a filter that retrieves only the information you need on an event being traced.
+
+## Set a trace filter
+
+1. If the trace is already running, execute `sp_trace_setstatus` by specifying `@status = 0` to stop the trace.
+
+1. Execute `sp_trace_setfilter` to configure the type of information to retrieve for the event being traced.
 
 > [!IMPORTANT]  
->  Unlike regular stored procedures, parameters of all [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] stored procedures (**sp_trace\__xx_**) are strictly typed and do not support automatic data type conversion. If these parameters are not called with the correct input parameter data types, as specified in the argument description, the stored procedure will return an error.  
-  
-## See Also  
- [Filter a Trace](../../relational-databases/sql-trace/filter-a-trace.md)   
- [sp_trace_setfilter (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-trace-setfilter-transact-sql.md)   
- [sp_trace_setstatus (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-trace-setstatus-transact-sql.md)   
- [System Stored Procedures (Transact-SQL)](../../relational-databases/system-stored-procedures/system-stored-procedures-transact-sql.md)   
- [SQL Server Profiler Stored Procedures (Transact-SQL)](../../relational-databases/system-stored-procedures/sql-server-profiler-stored-procedures-transact-sql.md)  
-  
-  
+> Unlike regular stored procedures, parameters of all [!INCLUDE [ssSqlProfiler](../../includes/sssqlprofiler-md.md)] stored procedures (`sp_trace_*`) are strictly typed and don't support automatic data type conversion. If these parameters aren't called with the correct input parameter data types, as specified in the argument description, the stored procedure will return an error.
+
+## Related content
+
+- [Filter a trace](filter-a-trace.md)
+- [sp_trace_setfilter (Transact-SQL)](../system-stored-procedures/sp-trace-setfilter-transact-sql.md)
+- [sp_trace_setstatus (Transact-SQL)](../system-stored-procedures/sp-trace-setstatus-transact-sql.md)
+- [System stored procedures (Transact-SQL)](../system-stored-procedures/system-stored-procedures-transact-sql.md)
+- [SQL Server Profiler stored procedures (Transact-SQL)](../system-stored-procedures/sql-server-profiler-stored-procedures-transact-sql.md)

docs/relational-databases/sql-trace/set-a-trace-filter-transact-sql.md

@@ -6572,33 +6572,33 @@ items:
     - name: SQL Trace
       href: relational-databases/sql-trace/sql-trace.md
       items:
-      - name: Create & Run Traces Using T-SQL Stored Procedures
+      - name: Create & run traces using T-SQL stored procedures
         href: relational-databases/sql-trace/create-and-run-traces-using-transact-sql-stored-procedures.md
-      - name: Create Manual Traces using Stored Procedures
+      - name: Create manual traces using stored procedures
         href: relational-databases/sql-trace/create-manual-traces-using-stored-procedures.md
-      - name: Save Trace Results to a File
+      - name: Save trace results to a file
         href: relational-databases/sql-trace/save-trace-results-to-a-file.md
-      - name: Improve Access to Trace Data
+      - name: Improve access to trace data
         href: relational-databases/sql-trace/improve-access-to-trace-data.md
-      - name: Create a Trace (T-SQL)
+      - name: Create a trace (T-SQL)
         href: relational-databases/sql-trace/create-a-trace-transact-sql.md
-      - name: Set a Trace Filter (T-SQL)
+      - name: Set a trace filter (T-SQL)
         href: relational-databases/sql-trace/set-a-trace-filter-transact-sql.md
-      - name: Modify an Existing Trace (T-SQL)
+      - name: Modify an existing Trace (T-SQL)
         href: relational-databases/sql-trace/modify-an-existing-trace-transact-sql.md
-      - name: View a Saved Trace (T-SQL)
+      - name: View a saved trace (T-SQL)
         href: relational-databases/sql-trace/view-a-saved-trace-transact-sql.md
-      - name: View Filter Information (T-SQL)
+      - name: View filter information (T-SQL)
         href: relational-databases/sql-trace/view-filter-information-transact-sql.md
-      - name: Delete a Trace (T-SQL)
+      - name: Delete a trace (T-SQL)
         href: relational-databases/sql-trace/delete-a-trace-transact-sql.md
-      - name: Optimize SQL Trace
+      - name: Optimize SQL trace
         href: relational-databases/sql-trace/optimize-sql-trace.md
-      - name: Filter a Trace
+      - name: Filter a trace
         href: relational-databases/sql-trace/filter-a-trace.md
-      - name: Limit Trace File & Table Sizes
+      - name: Limit trace file & table sizes
         href: relational-databases/sql-trace/limit-trace-file-and-table-sizes.md
-      - name: Schedule Traces
+      - name: Schedule traces
         href: relational-databases/sql-trace/schedule-traces.md
     - name: Query Store
       items:
@@ -9897,20 +9897,21 @@ items:
         href: tools/sql-server-profiler/analyze-deadlocks-with-sql-server-profiler.md
       - name: Analyze Queries with SHOWPLAN Results in SQL Server Profiler
         href: tools/sql-server-profiler/analyze-queries-with-showplan-results-in-sql-server-profiler.md
-    - name: Filter Traces
-      href: tools/sql-server-profiler/filter-traces-with-sql-server-profiler.md
+    - name: Filter traces
       items:
-      - name: Filter Events in a Trace
+      - name: Overview
+        href: tools/sql-server-profiler/filter-traces-with-sql-server-profiler.md
+      - name: Filter events in a trace
         href: tools/sql-server-profiler/filter-events-in-a-trace-sql-server-profiler.md
-      - name: View Filter Information
+      - name: View filter information
         href: tools/sql-server-profiler/view-filter-information-sql-server-profiler.md
-      - name: Modify a Filter
+      - name: Modify a filter
         href: tools/sql-server-profiler/modify-a-filter-sql-server-profiler.md
-      - name: Filter Events Based on the Event Start Time
+      - name: Filter events based on the event start time
         href: tools/sql-server-profiler/filter-events-based-on-the-event-start-time-sql-server-profiler.md
-      - name: Filter Events Based on the Event End Time
+      - name: Filter events based on the event end time
         href: tools/sql-server-profiler/filter-events-based-on-the-event-end-time-sql-server-profiler.md
-      - name: Filter Server Process IDs (SPIDs) in a Trace
+      - name: Filter server process IDs (SPIDs) in a trace
         href: tools/sql-server-profiler/filter-server-process-ids-spids-in-a-trace-sql-server-profiler.md
     - name: Save traces & templates
       href: tools/sql-server-profiler/save-traces-and-trace-templates.md

docs/toc.yml

@@ -1,61 +1,59 @@
 ---
-title: Filter Events in a Trace
+title: Filter events in a trace
 titleSuffix: SQL Server Profiler
 description: Find out how to set a filter to limit the events that SQL Server Profiler captures during a trace. Read about the formats required for certain filters.
 author: markingmyname
 ms.author: maghan
-ms.date: 04/11/2023
+ms.reviewer: randolphwest
+ms.date: 07/17/2024
 ms.service: sql
 ms.subservice: profiler
 ms.topic: conceptual
 ---
 
-# Filter Events in a Trace (SQL Server Profiler)
+# Filter events in a trace (SQL Server Profiler)
 
 [!INCLUDE [SQL Server Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdbmi.md)]
 
-Filters limit the events collected in a trace. If a filter is not set, all events of the selected event classes are returned in the trace output. It is not mandatory to set a filter for a trace. However, a filter minimizes the overhead that is incurred during tracing.
+Filters limit the events collected in a trace. If a filter isn't set, all events of the selected event classes are returned in the trace output. It's not mandatory to set a filter for a trace. However, a filter minimizes the overhead that is incurred during tracing.
 
- You add filters to trace definitions by using the **Events Selection** tab of the **Trace Properties** or **Trace Template Properties** dialog box.
+You add filters to trace definitions by using the **Events Selection** tab of the **Trace Properties** or **Trace Template Properties** dialog box.
 
 ## Filter events in a trace
 
 1. In the **Trace Properties** or **Trace Template Properties** dialog box, select the **Events Selection** tab.
 
-     The **Events Selection** tab contains a grid control. The grid control is a table that contains each of the traceable event classes. The table contains one row for each event class. The event classes may differ slightly, depending on the type and version of server to which you are connected. The event classes are identified in the **Events** column of the grid and are grouped by event category. The remaining columns list the data columns that can be returned for each event class.
+   The **Events Selection** tab contains a grid control. The grid control is a table that contains each of the traceable event classes. The table contains one row for each event class. The event classes might differ slightly, depending on the type and version of server to which you connect. The event classes are identified in the **Events** column of the grid and are grouped by event category. The remaining columns list the data columns that can be returned for each event class.
 
 1. Select **Column Filters.**
 
-     The **Edit Filter** dialog box appears. The **Edit Filter** dialog box contains a list of comparison operators that you can use to filter events in a trace.
+   The **Edit Filter** dialog box appears. The **Edit Filter** dialog box contains a list of comparison operators that you can use to filter events in a trace.
 
 1. To apply a filter, select the comparison operator, and type a value to use for the filter.
 
 1. Select **OK**.
 
- **Considerations:**
+### Considerations
 
-- If you set filter conditions on the **StartTime** and **EndTime** data columns of the Events Selection tab, then make sure that:
+If you set filter conditions on the **StartTime** and **EndTime** data columns of the Events Selection tab, then make sure that:
 
-  - The date you enter matches this format: `YYYY/MM/DD HH:mm:sec`.
+- The date you enter matches this format: `YYYY/MM/DD HH:mm:sec`.
 
-     -OR-
+  -OR-
 
-  - **Use regional settings to display date and time values** is checked in the **General Options** dialog box. To view the **General Options** dialog box, on the [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] **Tools** menu, select **Option**.
+- **Use regional settings to display date and time values** is checked in the **General Options** dialog box. To view the **General Options** dialog box, on the [!INCLUDE [ssSqlProfiler](../../includes/sssqlprofiler-md.md)] **Tools** menu, select **Option**.
 
-     -AND-
+  -AND-
 
-    - The date you enter is between January 1, 1753 and December 31, 9999.
+  - The date you enter is between January 1, 1753 and December 31, 9999.
 
-- If tracing events from the **osql** utility or from the **sqlcmd** utility, always append **%** to filters on the **TextData** data column.
+If tracing events from the **osql** utility or from the **sqlcmd** utility, always append **%** to filters on the **TextData** data column.
 
-> [!NOTE]
-> The checkbox for **Exclude rows that do not contain values** may filter out rows with:
->
-> - NULL values
-> - Empty strings (which technically are values)
+The checkbox for **Exclude rows that don't contain values** might filter out rows with the following conditions, while NOT filtering out events where the column itself isn't present:
 
-while NOT filtering out events where the column itself is not present.
+- `NULL` values
+- Empty strings (which technically are values)
 
-## Next steps
+## Related content
 
-- [SQL Server Profiler](../../tools/sql-server-profiler/sql-server-profiler.md)
+- [SQL Server Profiler](sql-server-profiler.md)

docs/tools/sql-server-profiler/filter-events-in-a-trace-sql-server-profiler.md

@@ -4,21 +4,25 @@ titleSuffix: SQL Server Profiler
 description: Find out how to define a filter so that SQL Server Profiler gathers the information you need during traces. Read about other advantages of trace filters.
 author: markingmyname
 ms.author: maghan
-ms.date: 03/01/2017
+ms.reviewer: randolphwest
+ms.date: 07/17/2024
 ms.service: sql
 ms.subservice: profiler
 ms.topic: conceptual
 ---
 
-# Filter Traces with SQL Server Profiler
- [!INCLUDE [SQL Server Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdbmi.md)]
-  You can define filters on data columns for [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] trace events so that information is captured only for those events that you are interested in. Trace filters reduce the impact of tracing on system performance because fewer events are captured in the trace. Filtering also makes trace output easier to read because there are fewer events to search through.  
-  
- **To filter traces with SQL Server Profiler**  
-  
- [Filter Events in a Trace (SQL Server Profiler)](../../tools/sql-server-profiler/filter-events-in-a-trace-sql-server-profiler.md)  
-  
-## See Also  
- [Filter a Trace](../../relational-databases/sql-trace/filter-a-trace.md)  
-  
-  
+# Filter traces with SQL Server Profiler
+
+[!INCLUDE [SQL Server Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdbmi.md)]
+
+You can define filters on data columns for [!INCLUDE [ssSqlProfiler](../../includes/sssqlprofiler-md.md)] trace events so that information is captured only for those events that you're interested in. Trace filters reduce the effect of tracing on system performance because fewer events are captured in the trace. Filtering also makes trace output easier to read because there are fewer events to search through.
+
+## Filter events in a trace with SQL Server Profiler
+
+- [Filter events in a trace (SQL Server Profiler)](filter-events-in-a-trace-sql-server-profiler.md)
+- [Modify a filter (SQL Server Profiler)](modify-a-filter-sql-server-profiler.md)
+
+## Related content
+
+- [Filter a trace](../../relational-databases/sql-trace/filter-a-trace.md)
+- [Set a trace filter (Transact-SQL)](../../relational-databases/sql-trace/set-a-trace-filter-transact-sql.md)

docs/tools/sql-server-profiler/filter-traces-with-sql-server-profiler.md

@@ -1,38 +1,38 @@
 ---
-title: Modify a Filter
+title: Modify a filter
 titleSuffix: SQL Server Profiler
 description: Learn how to modify a trace filter in SQL Server Profiler so you can gather the information you need. Read about how trace filters affect database performance.
 author: markingmyname
 ms.author: maghan
-ms.date: 03/01/2017
+ms.reviewer: randolphwest
+ms.date: 07/17/2024
 ms.service: sql
 ms.subservice: profiler
 ms.topic: conceptual
 ---
 
-# Modify a Filter (SQL Server Profiler)
-
- [!INCLUDE [SQL Server Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdbmi.md)]
-
-You add filters to trace templates, which contain the trace definitions, to limit the number of events that are gathered by a trace. Limiting the number of events gathered can reduce the performance effects of tracing. If you set filters for a trace template and find that the trace is not gathering the kind of information that you need, you can edit the filter.  
-  
-### To modify a filter  
-  
-1.  In [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)], open the template for the trace filter that you want to modify. On the **File** menu, click **Templates**, and then choose **Edit Template**.  
-  
-2.  In the **General** tab of the **Trace Template Properties** dialog, select a template from the **Select template name** list.  
-  
-3.  Click the **Events Selection** tab.  
-  
-     The **Events Selection** tab contains a grid control. The grid control is a table that contains each of the traceable event classes. The table contains one row for each event class. The event classes may differ slightly, depending on the type and version of server to which you are connected. The event classes are identified in the **Events**column of the grid and are grouped by event category. The remaining columns list the data columns that can be returned for each event class.  
-  
-4.  Click **Column Filters**.  
-  
-5.  In the **Edit Filter** dialog box, click the value next to the comparison operator that you want to edit, and type the new value or delete a value. You can also add additional filters.  
-  
-6.  Click **OK** and save the template.  
-  
-## See Also  
- [SQL Server Profiler](../../tools/sql-server-profiler/sql-server-profiler.md)  
-  
-  
+# Modify a filter (SQL Server Profiler)
+
+[!INCLUDE [SQL Server Azure SQL Managed Instance](../../includes/applies-to-version/sql-asdbmi.md)]
+
+You add filters to trace templates, which contain the trace definitions, to limit the number of events gathered by a trace. Limiting the number of events gathered can reduce the performance effects of tracing. If you set filters for a trace template, and find that the trace isn't gathering the kind of information that you need, you can edit the filter.
+
+## Modify a filter
+
+1. In [!INCLUDE [ssSqlProfiler](../../includes/sssqlprofiler-md.md)], open the template for the trace filter that you want to modify. On the **File** menu, select **Templates**, and then choose **Edit Template**.
+
+1. In the **General** tab of the **Trace Template Properties** dialog, select a template from the **Select template name** list.
+
+1. Select the **Events Selection** tab.
+
+   The **Events Selection** tab contains a grid control. The grid control is a table that contains each of the traceable event classes. The table contains one row for each event class. The event classes might differ slightly, depending on the type and version of server to which you connect. The event classes are identified in the **Events** column of the grid and are grouped by event category. The remaining columns list the data columns that can be returned for each event class.
+
+1. Select **Column Filters**.
+
+1. In the **Edit Filter** dialog box, select the value next to the comparison operator that you want to edit, and type the new value or delete a value. You can also add extra filters.
+
+1. Select **OK** and save the template.
+
+## Related content
+
+- [SQL Server Profiler](sql-server-profiler.md)