anchor.diff:  // ModuleID: debezium-sql-server-connector-running-an-offline-update-after-a-schema-change
   // Title: Running an offline update after a schema change
   [id="offline-schema-updates"]
  -==== Offline schema updates
  +=== Offline schema updates
   
   Offline schema updates provide the safest method for updating capture tables.
   However, offline updates might not be feasible for use with applications that require high-availability.
  
positive.code: // ModuleID: debezium-sql-server-connector-running-an-online-update-after-a-schema-change
  // Title: Running an online update after a schema change
  [id="online-schema-updates"]
  ==== Online schema updates
  
  The procedure for completing an online schema updates is simpler than the procedure for running an offline schema update,
  and you can complete it without requiring any downtime in application and data processing.
  
negative.code: 
  endif::community[]
  
  For the complete list of the configuration properties that you can set for the {prodname} SQL Server connector, see {link-prefix}:{link-sqlserver-connector}#sqlserver-connector-properties[SQL Server connector properties].
  
  ifdef::community[]
  You can send this configuration with a `POST` command to a running Kafka Connect service.
  The service records the configuration and start up the one connector task that performs the following tasks:
  
  * Connects to the SQL Server database.
  * Reads the transaction log.
  * Records change events to Kafka topics.
  
  [[sqlserver-adding-connector-configuration]]
  === Adding connector configuration
  
  To start running a {prodname} SQL Server connector, create a connector configuration, and add the configuration to your Kafka Connect cluster.
  
  .Prerequisites
  
  * {link-prefix}:{link-sqlserver-connector}#setting-up-sqlserver[CDC is enabled on SQL Server].
  * The {prodname} SQL Server connector is installed.
  
  .Procedure
  
  . Create a configuration for the SQL Server connector.
  
  . Use the link:{link-kafka-docs}/#connect_rest[Kafka Connect REST API] to add that connector configuration to your Kafka Connect cluster.
  endif::community[]
  
  .Results
  
  When the connector starts, it {link-prefix}:{link-sqlserver-connector}#sqlserver-snapshots[performs a consistent snapshot] of the SQL Server databases that the connector is configured for.
  The connector then starts generating data change events for row-level operations and streaming the change event records to Kafka topics.
  
  // Type: reference
  // Title: Descriptions of {prodname} SQL Server connector configuration properties
  [[sqlserver-connector-properties]]
  === Connector properties
  
  The {prodname} SQL Server connector has numerous configuration properties that you can use to achieve the right connector behavior for your application.
  Many properties have default values.
  
  The following configuration properties are _required_ unless a default value is available.
  
  