anchor.diff:  
   // Type: assembly
   // ModuleID: setting-up-sql-server-for-use-with-the-debezium-sql-server-connector
  -//Title: Setting up SQL Server for use with the {prodname} connector
  +//Title: Setting up SQL Server to run a {prodname} connector
   [[setting-up-sqlserver]]
   == Setting up SQL Server
   
  
positive.code: 
  Be sure to consult the {link-kafka-docs}.html[Kafka documentation] for all of the configuration properties for Kafka producers and consumers. (The SQL Server connector does use the {link-kafka-docs}.html#newconsumerconfigs[new consumer].)
  
  
  // Type: assembly
  // ModuleID: refreshing-capture-tables-after-a-schema-change
  // Title: Refreshing capture tables after a schema change
  [[sqlserver-schema-evolution]]
  === Database schema evolution
  
  When change data capture is enabled for a SQL Server table, as changes occur in the table, event records are persisted to a capture table on the server.
  If you introduce a change in the structure of the source table change, for example, by adding a new column, that change is not dynamically reflected in the change table.
  
negative.code: // ModuleID: monitoring-debezium-sql-server-connector-performance
  // Title: Monitoring {prodname} SQL Server connector performance
  [[sqlserver-monitoring]]
  == Monitoring
  
  The {prodname} SQL Server connector provides three types of metrics that are in addition to the built-in support for JMX metrics that Zookeeper, Kafka, and Kafka Connect provide.
  The connector provides the following metrics:
  