anchor.diff:  === Data types
   
   As described above, the SQL Server connector represents the changes to rows with events that are structured like the table in which the row exist.
  -The event contains a field for each column value, and how that value is represented in the event depends on the MySQL data type of the column. This section describes this mapping.
  +The event contains a field for each column value, and how that value is represented in the event depends on the SQL data type of the column. This section describes this mapping.
   
   The following table describes how the connector maps each of the SQL Server data types to a _literal type_ and _semantic type_ within the events' fields.
   Here, the _literal type_ describes how the value is literally represented using Kafka Connect schema types, namely `INT8`, `INT16`, `INT32`, `INT64`, `FLOAT32`, `FLOAT64`, `BOOLEAN`, `STRING`, `BYTES`, `ARRAY`, `MAP`, and `STRUCT`.
  
positive.code: Please bear in mind that _CDC_ cannot be enabled for `master` database.
  [source,sql]
  ----
  -- ====  
  -- Enable Database for CDC template   
  -- ====  
  USE MyDB  
  GO  
  EXEC sys.sp_cdc_enable_db  
  GO
  ----
  
  Then enable _CDC_ for each table that you plan to monitor
  [source,sql]
  ----
  -- =========  
  -- Enable a Table Specifying Filegroup Option Template  
  -- =========  
  USE MyDB  
  GO  
  
  EXEC sys.sp_cdc_enable_table  
  @source_schema = N'dbo',  
  @source_name   = N'MyTable',  
  @role_name     = N'MyRole',  
  @filegroup_name = N'MyDB_CT',  
  @supports_net_changes = 1  
  GO
  ----
  
  
negative.code: 
  See the link:#connector-properties[complete list of connector properties] that can be specified in these configurations.
  
  This configuration can be sent via POST to a running Kafka Connect service, which will then record the configuration and start up the one connector task that will connect to the SQL Server database, read the transaction log, and record events to Kafka topics.
  
  
  [[connector-properties]]
  