Merge pull request #16205 from DennisLee-DennisLee/v-dele-1750982-007

1750982: 7th batch. 22 files with table column header fixes.

Author: megvanhuygen

docs/data-quality-services/building-a-knowledge-base.md

@@ -19,7 +19,7 @@ ms.author: sawinark
 ## In This Section  
  You can perform the following operations on a knowledge base:  
 
-|||  
+|Operation Description|Topic|  
 |-|-|  
 |Create a new knowledge base from scratch, from an existing knowledge base, or from a .dqs data file.|[Create a Knowledge Base](../data-quality-services/create-a-knowledge-base.md)|  
 |Open an existing knowledge base to perform knowledge discovery, domain management, or add a matching policy.|[Open a Knowledge Base](../data-quality-services/open-a-knowledge-base.md)|  

docs/data-quality-services/data-matching.md

@@ -67,7 +67,7 @@ ms.author: sawinark
 ## In This Section  
  You can perform the following tasks related to matching in DQS:  
 
-|||  
+|Task Description|Topic|  
 |-|-|  
 |Create and test matching rules in a matching policy|[Create a Matching Policy](../data-quality-services/create-a-matching-policy.md)|  
 |Run matching in a data quality project|[Run a Matching Project](../data-quality-services/run-a-matching-project.md)|  

docs/data-quality-services/dqs-knowledge-bases-and-domains.md

@@ -140,7 +140,7 @@ ms.author: sawinark
 ## In This Section  
  You can perform the following operations on a knowledge base and its domains:  
 
-|||  
+|Operation Description|Topic|  
 |-|-|  
 |Create, open, add knowledge to, and perform discovery on a knowledge base|[Building a Knowledge Base](../data-quality-services/building-a-knowledge-base.md)|  
 |Perform import and export operations on domains and knowledge bases|[Importing and Exporting Knowledge](../data-quality-services/importing-and-exporting-knowledge.md)|  

docs/data-quality-services/importing-and-exporting-knowledge.md

@@ -22,7 +22,7 @@ ms.author: sawinark
 ## In This Section  
  You can perform the following import and export operations:  
 
-|||  
+|Operation Description|Topic|  
 |-|-|  
 |Export a domain in a knowledge base to a .dqs data file|[Export a Domain to a .dqs File](../data-quality-services/export-a-domain-to-a-dqs-file.md)|  
 |Import a domain from a .dqs data file into an existing knowledge base|[Import a Domain from a .dqs File](../data-quality-services/import-a-domain-from-a-dqs-file.md)|  

docs/data-quality-services/managing-a-composite-domain.md

@@ -23,7 +23,7 @@ ms.author: sawinark
 ## In This Section  
  Using a composite domain enables you to do the following:  
 
-|||  
+|Operation Description|Topic|  
 |-|-|  
 |Create a semantic representation for a data field that consists of multiple related terms that are not parsed|[Create a Composite Domain](../data-quality-services/create-a-composite-domain.md)|  
 |When you are mapping complex data to a composite domain, you can parse the data based on knowledge, in addition to parsing on a delimiter. DQS will first attempt to use its knowledge about single domains to determine how parts of the complex string belong in single domains.|[Create a Composite Domain](../data-quality-services/create-a-composite-domain.md)|  

docs/data-quality-services/managing-a-domain.md

@@ -38,7 +38,7 @@ ms.author: sawinark
 ## In This Section  
  Using a domain enables you to do the following:  
 
-|||  
+|Operation Description|Topic|  
 |-|-|  
 |Create a semantic representation for a data field with a specific data type, specify how the domain is populated, and format the output of the domain|[Create a Domain](../data-quality-services/create-a-domain.md)|  
 |Link a domain to another domain, enabling it to share the same settings and values|[Create a Linked Domain](../data-quality-services/create-a-linked-domain.md)|  

docs/database-engine/availability-groups/windows/monitor-performance-for-always-on-availability-groups.md

@@ -20,28 +20,26 @@ ms.author: jroth
 
  ![Availability group data synchronization](media/always-onag-datasynchronization.gif "Availability group data synchronization")  
 
-|||||  
+|Sequence|Step description|Comments|Useful metrics|  
 |-|-|-|-|  
-|**Sequence**|**Step description**|**Comments**|**Useful metrics**|  
 |1|Log generation|Log data is flushed to disk. This log must be replicated to the secondary replicas. The log records enter the send queue.|[SQL Server:Database > Log bytes flushed\sec](~/relational-databases/performance-monitor/sql-server-databases-object.md)|  
 |2|Capture|Logs for each database is captured and sent to the corresponding partner queue (one per database-replica pair). This capture process runs continuously as long as the availability replica is connected and data movement is not suspended for any reason, and the database-replica pair is shown to be either Synchronizing or Synchronized. If the capture process is not able to scan and enqueue the messages fast enough, the log send queue builds up.|[SQL Server:Availability Replica > Bytes Sent to Replica\sec](~/relational-databases/performance-monitor/sql-server-availability-replica.md), which is an aggregation of the sum of all database messages queued for that availability replica.<br /><br /> [log_send_queue_size](~/relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md) (KB) and [log_bytes_send_rate](~/relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md) (KB/sec) on the primary replica.|  
 |3|Send|The messages in each database-replica queue is dequeued and sent across the wire to the respective secondary replica.|[SQL Server:Availability Replica > Bytes sent to transport\sec](~/relational-databases/performance-monitor/sql-server-availability-replica.md)|  
 |4|Receive and cache|Each secondary replica receives and caches the message.|Performance counter [SQL Server:Availability Replica > Log Bytes Received/sec](~/relational-databases/performance-monitor/sql-server-availability-replica.md)|  
-|5|Harden|Log is flushed on the secondary replica for hardening. After the log flush, an acknowledgement is sent back to the primary replica.<br /><br /> Once the log is hardened, data loss is avoided.|Performance counter [SQL Server:Database > Log Bytes Flushed/sec](~/relational-databases/performance-monitor/sql-server-databases-object.md)<br /><br /> Wait type [HADR_LOGCAPTURE_SYNC](~/relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md)|  
+|5|Harden|Log is flushed on the secondary replica for hardening. After the log flush, an acknowledgment is sent back to the primary replica.<br /><br /> Once the log is hardened, data loss is avoided.|Performance counter [SQL Server:Database > Log Bytes Flushed/sec](~/relational-databases/performance-monitor/sql-server-databases-object.md)<br /><br /> Wait type [HADR_LOGCAPTURE_SYNC](~/relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md)|  
 |6|Redo|Redo the flushed pages on the secondary replica. Pages are kept in the redo queue as they wait to be redone.|[SQL Server:Database Replica > Redone Bytes/sec](~/relational-databases/performance-monitor/sql-server-database-replica.md)<br /><br /> [redo_queue_size](~/relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md) (KB) and [redo_rate](~/relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md).<br /><br /> Wait type [REDO_SYNC](~/relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md)|  
 
 ##  Flow control gates  
  Availability groups are designed with flow control gates on the primary replica to avoid excessive resource consumption, such as network and memory resources, on all availability replicas. These flow control gates do not affect the synchronization health state of the availability replicas, but they can affect the overall performance of your availability databases, including RPO.  
 
  After the logs have been captured on the primary replica, they are subject to two levels of flow controls, as shown in the following table.  
 
-|||||  
+|Level|Number of gates|Number of messages|Useful metrics|  
 |-|-|-|-|  
-|**Level**|**Number of gates**|**Number of messages**|**Useful metrics**|  
 |Transport|1 per availability replica|8192|Extended event **database_transport_flow_control_action**|  
 |Database|1 per availability database|11200 (x64)<br /><br /> 1600 (x86)|[DBMIRROR_SEND](~/relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md)<br /><br /> Extended event **hadron_database_flow_control_action**|  
 
- Once the message threshold of either gate is reached, log messages are no longer sent to a specific replica or for a specific database. Messages can be sent once acknowledgement messages are received for the sent messages to bring the number of sent messages below the threshold.  
+ Once the message threshold of either gate is reached, log messages are no longer sent to a specific replica or for a specific database. Messages can be sent once acknowledgment messages are received for the sent messages to bring the number of sent messages below the threshold.  
 
  In addition to the flow control gates, there is another factor that can prevent the log messages from being sent. The synchronization of replicas ensures that the messages are sent and applied in the order of the log sequence numbers (LSN). Before a log message is sent, its LSN also checked against the lowest acknowledged LSN number to make sure that it is less than one of thresholds (depending on the message type). If the gap between the two LSN numbers is larger than the threshold, the messages are not sent. Once the gap is below the threshold again, the messages are sent.  
 

docs/database-engine/availability-groups/windows/secondary-replica-connection-redirection-always-on-availability-groups.md

@@ -56,7 +56,7 @@ In [!INCLUDE[sssqlv15-md](../../../includes/sssqlv15-md.md)], `READ_WRITE_ROUTIN
 
 By default, read/write replica connection redirection is not set for a replica. The way a secondary replica handles connection requests depends on whether or not the secondary replica is set to allow connections and on the `ApplicationIntent` setting in the connection string. The following table shows how a secondary replica handles connections based on `SECONDARY_ROLE (ALLOW CONNECTIONS = )` and `ApplicationIntent`.
 
-||`SECONDARY_ROLE (ALLOW CONNECTIONS = NO)`|`SECONDARY_ROLE (ALLOW CONNECTIONS = READ_ONLY)`|`SECONDARY_ROLE (ALLOW CONNECTIONS = ALL)`|
+|`ApplicationIntent` value|`SECONDARY_ROLE (ALLOW CONNECTIONS = NO)`|`SECONDARY_ROLE (ALLOW CONNECTIONS = READ_ONLY)`|`SECONDARY_ROLE (ALLOW CONNECTIONS = ALL)`|
 |-----|-----|-----|-----|
 |`ApplicationIntent=ReadWrite`<br/> Default|Connections fail|Connections fail|Connections succeed<br/>Reads succeed<br/>Writes fail|
 |`ApplicationIntent=ReadOnly`|Connections fail|Connections succeed|Connections succeed
@@ -67,7 +67,7 @@ The preceding table shows the default behavior, which is the same as versions of
 
 After you set read/write connection redirection, the way the replica handles connection requests behaves differently. The connection behavior still depends on `SECONDARY_ROLE (ALLOW CONNECTIONS = )` and `ApplicationIntent` setting. The following table shows how a secondary replica with `READ_WRITE_ROUTING` set handles connections based on `SECONDARY_ROLE (ALLOW CONNECTIONS = )` and `ApplicationIntent`.
 
-||`SECONDARY_ROLE (ALLOW CONNECTIONS = NO)`|`SECONDARY_ROLE (ALLOW CONNECTIONS = READ_ONLY)`|`SECONDARY_ROLE (ALLOW CONNECTIONS = ALL)`|
+|`ApplicationIntent` value|`SECONDARY_ROLE (ALLOW CONNECTIONS = NO)`|`SECONDARY_ROLE (ALLOW CONNECTIONS = READ_ONLY)`|`SECONDARY_ROLE (ALLOW CONNECTIONS = ALL)`|
 |-----|-----|-----|-----|
 |`ApplicationIntent=ReadWrite`<br/>Default|Connections fail|Connections fail|Connections route to primary|
 |`ApplicationIntent=ReadOnly`|Connections fail|Connections succeed|Connections succeed

docs/database-engine/configure-windows/backup-checksum-default.md

@@ -19,9 +19,8 @@ ms.author: maghan
 
  The possible values are described in the following table:  
 
-|||  
+|Value|Meaning|  
 |-|-|  
-|**Value**|**Meaning**|  
 |0|Disabled. This is the default setting.|  
 |1|Enabled|  
 

docs/database-engine/configure-windows/buffer-pool-extension.md

@@ -92,9 +92,8 @@ ms.author: maghan
 
 ## Related Tasks  
 
-|||  
+|Task Description|Topic|  
 |-|-|  
-|**Task Description**|**Topic**|  
 |Enable and configure the buffer pool extension.|[ALTER SERVER CONFIGURATION (Transact-SQL)](../../t-sql/statements/alter-server-configuration-transact-sql.md)|  
 |Modify the buffer pool extension configuration|[ALTER SERVER CONFIGURATION (Transact-SQL)](../../t-sql/statements/alter-server-configuration-transact-sql.md)|  
 |View the buffer pool extension configuration|[sys.dm_os_buffer_pool_extension_configuration (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-os-buffer-pool-extension-configuration-transact-sql.md)|