anchor.diff:  
   |[[sqlserver-property-database-history-kafka-bootstrap-servers]]<<sqlserver-property-database-history-kafka-bootstrap-servers, `database.history{zwsp}.kafka.bootstrap{zwsp}.servers`>>
   |
  -|A list of host/port pairs that the connector will use for establishing an initial connection to the Kafka cluster.
  +|A list of host and port pairs that the connector will use for establishing an initial connection to the Kafka cluster.
   This connection is used for retrieving database schema history previously stored by the connector, and for writing each DDL statement read from the source database. This should point to the same Kafka cluster used by the Kafka Connect process.
   
   |[[sqlserver-property-table-whitelist]]
  
positive.code: [[setting-up-sqlserver]]
  == Setting up SQL Server
  
  Before using the SQL Server connector to monitor the changes committed on SQL Server, first enable _CDC_ on a monitored database.
  Please bear in mind that _CDC_ cannot be enabled for the `primary` database.
  
  // Type: procedure
  // ModuleID: enabling-cdc-on the-sql-server-database
  === Enabling CDC on the SQL Server database
  
  .Example: Enabling a SQL Server database for the CDC template
  [source,sql]
  ----
  -- ====
  -- Enable Database for CDC template
  -- ====
  USE MyDB
  GO
  EXEC sys.sp_cdc_enable_db
  
negative.code: [[sqlserver-transaction-metadata]]
  === Transaction metadata
  
  {prodname} can generate events that represent transaction boundaries and that enrich data change event messages. 
  
  Database transactions are represented by a statement block that is enclosed between the `BEGIN` and `END` keywords. 
  {prodname} generates transaction boundary events for the `BEGIN` and `END` delimiters in every transaction. 
  Transaction boundary events contain the following fields: 
  
  `status`:: `BEGIN` or `END`
  `id`:: String representation of unique transaction identifier.
  `event_count` (for `END` events):: Total number of events emitted by the transaction.
  `data_collections` (for `END` events):: An array of pairs of `data_collection` and `event_count` that provides the number of events emitted by changes originating from given data collection.
  
  The following example shows a typical transaction boundary message:
  
  .Example: SQL Server connector transaction boundary event
  [source,json,indent=0,subs="+attributes"]
  ----
  {
  