[Issues] Fix multiple files due to correcting git issues

Author: markingmyname

docs/includes/ssms-old-versions-16.md

@@ -0,0 +1,10 @@
+---
+author: markingmyname
+ms.author: maghan
+ms.date: 04/11/2023
+ms.service: sql
+ms.subservice: ssms
+ms.topic: include
+---
+
+This feature works with SSMS version 16.5.3 and earlier.

docs/relational-databases/import-export/specify-data-formats-for-compatibility-when-using-bcp-sql-server.md

@@ -3,36 +3,41 @@ title: "Options (SQL Server Object Explorer - Commands)"
 description: "Options (SQL Server Object Explorer - Commands)"
 author: "markingmyname"
 ms.author: "maghan"
-ms.date: "01/19/2017"
+ms.date: 04/11/2023
 ms.service: sql
 ms.subservice: ssms
 ms.topic: conceptual
 f1_keywords:
-  - "VS.ToolsOptionsPages.Sql_Server_Object_Explorer.ObjectExplorerCommands"
+  - "VS.ToolsOptionsPages.SQL_Server_Object_Explorer.Commands"
 ---
+
 # Options (SQL Server Object Explorer - Commands)
+
 [!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
-When you right-click a table or view in Object Explorer, the following two options for displaying rows in the table are presented:  
-  
--   **Select Top 1000 Rows**  
-  
-    Creates a script in the Query Editor that selects the top 1000 rows.  
-  
--   **Edit Top 200 Rows**  
-  
-    Opens the table in the Visual Database Tools with 200 rows populated.  
-  
-Use the **General Scripting Options** dialog box to change the number of rows that will be opened.  
-  
-## General Scripting Options  
+
+When you right-click a table or view in Object Explorer, the following two options for displaying rows in the table are presented:
+
+- **Select Top 1000 Rows**
+
+    Creates a script in the Query Editor that selects the top 1000 rows.
+
+- **Edit Top 200 Rows**
+
+    Opens the table in the Visual Database Tools with 200 rows populated.
+
+Use the **General Scripting Options** dialog box to change the number of rows that will be opened.
+
+## General Scripting Options
+
 **Value for Select Top \<n\> Audit record command**  
-Specifies the number of audit rows to return. The default is 1000 rows  
-  
+Specifies the number of audit rows to return. The default is 1000 rows
+
 **Value for Edit Top \<n\> Rows command**  
-Specifies the number of rows to return when you are editing rows in a table. The default is 200 rows.  
-  
+Specifies the number of rows to return when you are editing rows in a table. The default is 200 rows.
+
 **Value for Select Top \<n\> Rows command**  
-Specifies the number of rows to be returned that is specified in the Query Editor script that is created. The default is 1000 rows.  
-  
-## See Also  
-[SQL Server Audit (Database Engine)](../../relational-databases/security/auditing/sql-server-audit-database-engine.md)  
+Specifies the number of rows to be returned that is specified in the Query Editor script that is created. The default is 1000 rows.
+
+## Next setps
+
+- [SQL Server Audit (Database Engine)](../../relational-databases/security/auditing/sql-server-audit-database-engine.md)

docs/relational-databases/import-export/specify-field-and-row-terminators-sql-server.md

@@ -4,51 +4,58 @@ 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: 03/01/2017
+ms.date: 04/11/2023
 ms.service: sql
 ms.subservice: profiler
 ms.topic: conceptual
 ---
 
 # 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.  
-  
- You add filters to trace definitions by using the **Events Selection** tab of the **Trace Properties** or **Trace Template Properties** dialog box.  
-  
-### To filter events in a trace  
-  
-1.  In the **Trace Properties** or **Trace Template Properties** dialog box, 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.  
-  
-2.  Click **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.  
-  
-3.  To apply a filter, click the comparison operator, and type a value to use for the filter.  
-  
-4.  Click **OK**.  
-  
- **Considerations:**  
-  
--   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`.  
-  
-         -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, click **Option**.  
-  
-         -AND-  
-  
-    -   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.  
-  
-## See Also  
- [SQL Server Profiler](../../tools/sql-server-profiler/sql-server-profiler.md)  
-  
-  
+[!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.
+
+ 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.
+
+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.
+
+1. To apply a filter, select the comparison operator, and type a value to use for the filter.
+
+1. Select **OK**.
+
+ **Considerations:**
+
+- 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`.
+
+     -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**.
+
+     -AND-
+
+    - 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.
+
+> [!NOTE]
+> The checkbox for **Exclude rows that do not contain values** may filter out rows with:
+>
+> - NULL values
+> - Empty strings (which technically are values)
+
+while NOT filtering out events where the column itself is not present.
+
+## Next steps
+
+- [SQL Server Profiler](../../tools/sql-server-profiler/sql-server-profiler.md)