anchor.diff:  apiVersion: kafka.strimzi.io/v1beta1 
     kind: KafkaConnector
     metadata:
  -    name: inventory-connector <1>
  +    name: inventory-connector // <1>
       labels: strimzi.io/cluster: my-connect-cluster
     spec:
  -    class: io.debezium.connector.sqlserver.SqlServerConnector <2>
  +    class: io.debezium.connector.sqlserver.SqlServerConnector // <2>
       config:  
  -      database.hostname: 192.168.99.100 <3>
  -      database.port: 1433 <4>
  -      database.user: debezium <5>
  -      database.password: dbz <6>
  -      database.dbname: testDB <7>
  -      database.server.name: fullfullment <8>
  -      database.include.list: dbo.customers <9>
  -      database.history.kafka.bootstrap.servers: my-cluster-kafka-bootstrap:9092 <10> 
  -      database.history.kafka.topic: dbhistory.fullfillment <11>
  -
  -----
  -<1> The name of our connector when we register it with a Kafka Connect service.
  -<2> The name of this SQL Server connector class.
  -<3> The address of the SQL Server instance.
  -<4> The port number of the SQL Server instance.
  -<5> The name of the SQL Server user
  -<6> The password for the SQL Server user
  -<7> The name of the database to capture changes from.
  -<8> The logical name of the SQL Server instance/cluster, which forms a namespace and is used in all the names of the Kafka topics to which the connector writes, the Kafka Connect schema names, and the namespaces of the corresponding Avro schema when the Avro converter is used.
  -<9> A list of all tables whose changes {prodname} should capture.
  -<10> The list of Kafka brokers that this connector will use to write and recover DDL statements to the database history topic.
  -<11> The name of the database history topic where the connector will write and recover DDL statements. This topic is for internal use only and should not be used by consumers.
  +      database.hostname: 192.168.99.100 // <3>
  +      database.port: 1433 // <4>
  +      database.user: debezium // <5>
  +      database.password: dbz // <6>
  +      database.dbname: testDB // <7>
  +      database.server.name: fullfullment // <8>
  +      database.include.list: dbo.customers // <9>
  +      database.history.kafka.bootstrap.servers: my-cluster-kafka-bootstrap:9092 // <10> 
  +      database.history.kafka.topic: dbhistory.fullfillment // <11>
  +
  +----
  +
  +.Descriptions of connector configuration settings
  +[cols="1,7",options="header",subs="+attributes"]
  +|===
  +|Item |Description
  +
  +|1
  +|The name of our connector when we register it with a Kafka Connect service.
  +
  +|2
  +|The name of this SQL Server connector class.
  +
  +|3
  +|The address of the SQL Server instance.
  +
  +|4
  +|The port number of the SQL Server instance.
  +
  +|5
  +|The name of the SQL Server user.
  +
  +|6
  +|The password for the SQL Server user.
  +
  +|7
  +|The name of the database to capture changes from.
  +
  +|8
  +|The logical name of the SQL Server instance/cluster, which forms a namespace and is used in all the names of the Kafka topics to which the connector writes, the Kafka Connect schema names, and the namespaces of the corresponding Avro schema when the Avro converter is used.
  +
  +|9
  +|A list of all tables whose changes {prodname} should capture.
  +
  +|10
  +|The list of Kafka brokers that this connector will use to write and recover DDL statements to the database history topic.
  +
  +|11
  +|The name of the database history topic where the connector will write and recover DDL statements. This topic is for internal use only and should not be used by consumers.
  +
  +|===
   
   endif::product[]
   
  
positive.code: 
  .Procedure
  
  . Create a configuration file 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. 
  
  
negative.code: === Adding connector configuration
  
  ifdef::community[]
  To run a {prodname} SQL Server connector, create a connector configuration and add the configuration to your Kafka Connect cluster. 
  
  .Prerequisites
  
  