Merge pull request #18949 from v-thepet/validations4

BULK VALIDATIONS fix column-header-missing 5th and last set

Author: ShannonLeavitt

docs/relational-databases/indexes/columnstore-indexes-what-s-new.md

@@ -42,7 +42,7 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 |Nonclustered columnstore index definition supports using a filtered condition|||yes|yes|yes|yes|yes|  
 |Compression delay option for columnstore indexes in `CREATE TABLE` and `ALTER TABLE`|||yes|yes|yes|yes|yes|
 |Columnstore index can have a non-persisted computed column||||yes|yes|||   
-|Tuple mover background merge support||||||yes|yes|yes|
+|Tuple mover background merge support|||||yes|yes|yes|
 
  <sup>1</sup> To create a read-only nonclustered columnstore index, store the index on a read-only filegroup.  
 

docs/relational-databases/maintenance-plans/options-in-the-back-up-database-task-for-maintenance-plan.md

@@ -92,7 +92,7 @@ ms.author: mikeray
  **Set backup compression**  
  In [!INCLUDE[ssEnterpriseEd10](../../includes/ssenterpriseed10-md.md)] (or a later version), select one the following [backup compression](../../relational-databases/backup-restore/backup-compression-sql-server.md) values:  
 
-|||  
+|Value|Description|  
 |-|-|  
 |**Use the default server setting**|Click to use the server-level default.<br /><br /> This default is set by the **backup compression default** server-configuration option. For information about how to view the current setting of this option,  see [View or Configure the backup compression default Server Configuration Option](../../database-engine/configure-windows/view-or-configure-the-backup-compression-default-server-configuration-option.md).|  
 |**Compress backup**|Click to compress the backup, regardless of the server-level default.<br /><br /> **\*\* Important \*\*** By default, compression significantly increases CPU usage, and the additional CPU consumed by the compression process might adversely affect concurrent operations. Therefore, you might want to create low-priority compressed backups in a session whose CPU usage is limited by [Resource Governor](../../relational-databases/resource-governor/resource-governor.md). For more information, see [Use Resource Governor to Limit CPU Usage by Backup Compression &#40;Transact-SQL&#41;](../../relational-databases/backup-restore/use-resource-governor-to-limit-cpu-usage-by-backup-compression-transact-sql.md).|  

docs/relational-databases/maintenance-plans/use-the-maintenance-plan-wizard.md

@@ -412,7 +412,7 @@ Generate a maintenance plan that runs this task against all [!INCLUDE[msCoName](
      **Set backup compression**  list  
      In [!INCLUDE[ssEnterpriseEd10](../../includes/ssenterpriseed10-md.md)] (or later versions), select one the following [backup compression](../../relational-databases/backup-restore/backup-compression-sql-server.md) values:  
 
-    |||  
+    |Value|Description|  
     |-|-|  
     |**Use the default server setting**|Click to use the server-level default. This default is set by the **backup compression default** server-configuration option. For information about how to view the current setting of this option, see [View or Configure the backup compression default Server Configuration Option](../../database-engine/configure-windows/view-or-configure-the-backup-compression-default-server-configuration-option.md).|  
     |**Compress backup**|Click to compress the backup, regardless of the server-level default.<br /><br /> **\*\* Important \*\*** By default, compression significantly increases CPU usage, and the additional CPU consumed by the compression process might adversely affect concurrent operations. Therefore, you might want to create low-priority compressed backups in a session whose CPU usage is limited by the Resource Governor. For more information, see [Use Resource Governor to Limit CPU Usage by Backup Compression &#40;Transact-SQL&#41;](../../relational-databases/backup-restore/use-resource-governor-to-limit-cpu-usage-by-backup-compression-transact-sql.md).|  

docs/relational-databases/native-client-ole-db-interfaces/ibcpsession2-bcpsetbulkmode.md

@@ -52,7 +52,7 @@ HRESULT BCPSetBulkMode (
 ## Returns  
  IBCPSession2::BCPSetBulkMode can return one of the following:  
 
-|||  
+|Value|Description|  
 |-|-|  
 |**S_OK**|The method succeeded.|  
 |**E_FAIL**|A provider specific error occurred, for detailed information use the ISQLServerErrorInfo interface.|  

docs/relational-databases/performance/performance-center-for-sql-server-database-engine-and-azure-sql-database.md

@@ -32,7 +32,7 @@ ms.author: wiassaf
 ## Configuration Options for Performance  
  [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] provides the ability to affect database engine performance  through a number of configuration options at the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] level. With [!INCLUDE[ssSDSFull](../../includes/sssdsfull-md.md)], Microsoft performs most, but not all, of these optimizations for you.  
 
-|||  
+|Options|Description|  
 |-|-|  
 |**Disk configuration options**|:::image type="icon" source="../../relational-databases/performance/media/security-center-sqlserver.png"::: [Disk striping and RAID](https://technet.microsoft.com/library/ms190764\(v=sql.105\).aspx)|  
 |**Data and log file configuration options**|:::image type="icon" source="../../relational-databases/performance/media/security-center-sqlserver.png"::: [Place Data and Log Files on Separate Drives](../../relational-databases/policy-based-management/place-data-and-log-files-on-separate-drives.md)<br />:::image type="icon" source="../../relational-databases/performance/media/security-center-sqlserver.png"::: [View or Change the Default Locations for Data and Log Files &#40;SQL Server Management Studio&#41;](../../database-engine/configure-windows/view-or-change-the-default-locations-for-data-and-log-files.md)|  
@@ -50,7 +50,7 @@ ms.author: wiassaf
 
 ## Query Performance Options  
 
-|||  
+|Option|Description|  
 |-|-|  
 |:::image type="icon" source="../../relational-databases/performance/media/security-center-both.png"::: **[Indexes](../../relational-databases/indexes/indexes.md)**|[Reorganize and Rebuild Indexes](../../relational-databases/indexes/reorganize-and-rebuild-indexes.md)<br />[Specify Fill Factor for an Index](../../relational-databases/indexes/specify-fill-factor-for-an-index.md)<br />[Configure Parallel Index Operations](../../relational-databases/indexes/configure-parallel-index-operations.md)<br />[SORT_IN_TEMPDB Option For Indexes](../../relational-databases/indexes/sort-in-tempdb-option-for-indexes.md)<br />[Improve the Performance of Full-Text Indexes](../../relational-databases/search/improve-the-performance-of-full-text-indexes.md)<br />[Configure the min memory per query Server Configuration Option](../../database-engine/configure-windows/configure-the-min-memory-per-query-server-configuration-option.md)<br />[Configure the index create memory Server Configuration Option](../../database-engine/configure-windows/configure-the-index-create-memory-server-configuration-option.md)|  
 |:::image type="icon" source="../../relational-databases/performance/media/security-center-both.png"::: **[Partitioned Tables and Indexes](../../relational-databases/partitions/partitioned-tables-and-indexes.md)**|[Benefits of Partitioning](../partitions/partitioned-tables-and-indexes.md)|  

docs/relational-databases/sql-server-transaction-locking-and-row-versioning-guide.md

@@ -515,9 +515,9 @@ GO
 
 <a name="lock_compat_table"></a> The following table shows the compatibility of the most commonly encountered lock modes.  
 
-||Existing granted mode||||||  
+|Existing granted mode|**IS**|**S**|**U**|**IX**|**SIX**|**X**|
 |------|---------------------------|------|------|------|------|------|  
-|**Requested mode**|**IS**|**S**|**U**|**IX**|**SIX**|**X**|  
+|**Requested mode**|
 |**Intent shared (IS)**|Yes|Yes|Yes|Yes|Yes|No|  
 |**Shared (S)**|Yes|Yes|Yes|No|No|No|  
 |**Update (U)**|Yes|Yes|No|No|No|No|  
@@ -558,9 +558,9 @@ GO
 
  Key-range lock modes have a compatibility matrix that shows which locks are compatible with other locks obtained on overlapping keys and ranges.  
 
-||Existing granted mode|||||||  
+|Existing granted mode|**S**|**U**|**X**|**RangeS-S**|**RangeS-U**|**RangeI-N**|**RangeX-X**|
 |------|---------------------------|------|------|------|------|------|------|  
-|**Requested mode**|**S**|**U**|**X**|**RangeS-S**|**RangeS-U**|**RangeI-N**|**RangeX-X**|  
+|**Requested mode**  
 |**Shared (S)**|Yes|Yes|No|Yes|Yes|Yes|No|  
 |**Update (U)**|Yes|No|No|Yes|No|Yes|No|  
 |**Exclusive (X)**|No|No|No|No|No|Yes|No|  

docs/relational-databases/system-catalog-views/sys-fulltext-semantic-language-statistics-database-transact-sql.md

@@ -29,9 +29,8 @@ ms.reviewer: mikeray
  You can query this view to find out about the semantic language statistics component required for semantic processing.  
 
 
-||||  
-|-|-|-|  
 |**Column name**|**Type**|**Description**|  
+|-|-|-|  
 |**database_id**|**int**|ID of the database, unique within an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].|  
 |**register_date**|**datetime**|Date the database was registered for semantic processing.|  
 |**registered_by**|**int**|ID of the server principal that registered the database for semantic processing.|  

docs/relational-databases/system-catalog-views/sys-pdw-permanent-table-mappings-transact-sql.md

@@ -23,8 +23,8 @@ Ties permanent user tables to internal object names by **object_id**.
 
 |Column Name|Data Type|Description|  
 |-----------------|---------------|-----------------|  
-|physical_name|**nvarchar(36)**|The physical name for the table.<br /><br /> **physical_name** and **object_id** form the key for this view.||  
-|object_id|**int**|The object ID for the table. See [sys.objects &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/sys-objects-transact-sql.md).<br /><br /> **physical_name** and **object_id** form the key for this view.||  
+|physical_name|**nvarchar(36)**|The physical name for the table.<br /><br /> **physical_name** and **object_id** form the key for this view.|  
+|object_id|**int**|The object ID for the table. See [sys.objects &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/sys-objects-transact-sql.md).<br /><br /> **physical_name** and **object_id** form the key for this view.|  
 
 ## See Also  
  [Azure Synapse Analytics and Parallel Data Warehouse Catalog Views](../../relational-databases/system-catalog-views/sql-data-warehouse-and-parallel-data-warehouse-catalog-views.md)   

docs/relational-databases/system-catalog-views/sys-workload-management-workload-groups-transact-sql.md

@@ -24,7 +24,7 @@ monikerRange: "=azure-sqldw-latest"
 |-----------------|---------------|-----------------|-----------|
 |group_id|**int**|Unique ID of the workload group. Is not nullable.||
 |name|**sysname**|Name of the workload group. Must be unique to the instance.  Is not nullable.||
-|importance|**nvarchar(128)**|Is the relative importance of a request in this workload group and across workload groups for shared resources. Is not nullable.|low, below_normal, normal (default), above_normal, high||
+|importance|**nvarchar(128)**|Is the relative importance of a request in this workload group and across workload groups for shared resources. Is not nullable.|low, below_normal, normal (default), above_normal, high|
 |min_percentage_resource|**tinyint**|Guaranteed amount of resources for requests in the workload group. Resources are not shared with other workload groups. Is not nullable.||
 |cap_percentage_resource|**tinyint**|Hard cap on the resource percentage allocation for requests in the workload group. Limits the maximum resources allocated to the specified level. The allowed range for value is from 1 through 100.||
 |request_min_resource_grant_percent|**decimal(5,2)**|Specifies the minimum amount of resources allocated to a request. The allowed range for value is from 0.75 to 100.||

docs/relational-databases/system-dynamic-management-views/sql-server-operating-system-related-dynamic-management-views-transact-sql.md

@@ -23,42 +23,25 @@ ms.author: wiassaf
 
 This section documents dynamic management views (DMV) that are associated with [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Operating System (SQLOS). SQLOS is responsible for managing operating system resources that are specific to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
 
-
-|  |  |
-|---------|---------|
-|**sys.dm_os_buffer_descriptors** | **sys.dm_os_buffer_pool_extension_configuration**|
-|**sys.dm_os_child_instances** | **sys.dm_os_cluster_nodes** |
-|**sys.dm_os_cluster_properties** | **sys.dm_os_dispatcher_pools** |
-|**sys.dm_os_enumerate_fixed_drives** | **sys.dm_os_host_info** |
-|**sys.dm_os_hosts** | **sys.dm_os_latch_stats** |
-|**sys.dm_os_loaded_modules** |**sys.dm_os_memory_brokers**|
-|**sys.dm_os_memory_cache_clock_hands**|**sys.dm_os_memory_cache_counters** |
-|**sys.dm_os_memory_cache_entries**|**sys.dm_os_memory_cache_hash_tables**|
-|**sys.dm_os_memory_clerks**|**sys.dm_os_memory_nodes**|
-|**sys.dm_os_nodes**|**sys.dm_os_performance_counters**|
-|**sys.dm_os_process_memory**|**sys.dm_os_schedulers**|
-|**sys.dm_os_server_diagnostics_log_configurations**|**sys.dm_os_spinlock_stats** |
-|**sys.dm_os_stacks**|**sys.dm_os_sys_info**|
-|**sys.dm_os_sys_memory**|**sys.dm_os_tasks**|
-|**sys.dm_os_threads** |**sys.dm_os_virtual_address_dump**|
-|**sys.dm_os_volume_stats**|**sys.dm_os_waiting_tasks**|
-|**sys.dm_os_wait_stats**|**sys.dm_os_windows_info**|
-|**sys.dm_os_workers** ||
-
-
-
-
-
-
-
+:::row:::
+   :::column span="":::
+      **sys.dm_os_buffer_descriptors**<br>      **sys.dm_os_buffer_pool_extension_configuration**<br>      **sys.dm_os_child_instances**<br>      **sys.dm_os_cluster_nodes** <br>      **sys.dm_os_cluster_properties**<br>      **sys.dm_os_dispatcher_pools** <br>      **sys.dm_os_enumerate_fixed_drives**<br>      **sys.dm_os_host_info** <br>      **sys.dm_os_hosts**<br>      **sys.dm_os_latch_stats** <br>      **sys.dm_os_loaded_modules**<br>      **sys.dm_os_memory_brokers**<br>      **sys.dm_os_memory_cache_clock_hands**<br>      **sys.dm_os_memory_cache_counters** <br>      **sys.dm_os_memory_cache_entries**<br>      **sys.dm_os_memory_cache_hash_tables**<br>      **sys.dm_os_memory_clerks**<br>      **sys.dm_os_memory_nodes**
+   :::column-end:::
+   :::column span="":::
+      **sys.dm_os_nodes**<br>      **sys.dm_os_performance_counters**<br>      **sys.dm_os_process_memory**<br>      **sys.dm_os_schedulers**<br>      **sys.dm_os_server_diagnostics_log_configurations**<br>      **sys.dm_os_spinlock_stats** <br>      **sys.dm_os_stacks**<br>      **sys.dm_os_sys_info**<br>      **sys.dm_os_sys_memory**<br>      **sys.dm_os_tasks**<br>      **sys.dm_os_threads**<br>      **sys.dm_os_virtual_address_dump**<br>      **sys.dm_os_volume_stats**<br>      **sys.dm_os_waiting_tasks**<br>      **sys.dm_os_wait_stats**<br>      **sys.dm_os_windows_info**<br>      **sys.dm_os_workers** 
+   :::column-end:::
+:::row-end:::
 
  The following [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Operating System-related dynamic management views are [!INCLUDE[ssInternalOnly](../../includes/ssinternalonly-md.md)].  
 
-|||  
-|-|-|  
-|**sys.dm_os_function_symbolic_name**|**sys.dm_os_ring_buffers**|  
-|**sys.dm_os_memory_allocations**|**sys.dm_os_sublatches**|  
-|**sys.dm_os_worker_local_storage**||  
+:::row:::
+   :::column span="":::
+      **sys.dm_os_function_symbolic_name**<br>      **sys.dm_os_ring_buffers**  <br>      **sys.dm_os_memory_allocations**
+   :::column-end:::
+   :::column span="":::
+      **sys.dm_os_sublatches**  <br>      **sys.dm_os_worker_local_storage**  
+   :::column-end:::
+:::row-end:::
 
 ## See Also  
  [Dynamic Management Views and Functions &#40;Transact-SQL&#41;](~/relational-databases/system-dynamic-management-views/system-dynamic-management-views.md)