anchor.diff:  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  
  +-- ====
  +-- 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  
  +-- =========
  +-- 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
   ----
   
  
positive.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 MySQL database, read the binlog, and record events to Kafka topics.
  
  
  [[connector-properties]]
  
negative.code: [[example-configuration]]
  === Example configuration
  
  Using the SQL Server connector is straightforward. Here is an example of the configuration for a connector instance that monitors a SQL Server server at port 3306 on 192.168.99.100, which we logically name `fullfillment`:
  
  [source,json]
  ----
  