anchor.diff:  |Indicates whether the event key must contain a value in its `payload` field. In this example, a value in the key's payload is required. A value in the key's payload field is optional when a table does not have a primary key.
   
   |4
  -|`server1.dbo.customers.Key`
  +|`server1.dbo{zwsp}.customers{zwsp}.Key`
   a|Name of the schema that defines the structure of the key's payload. This schema describes the structure of the primary key for the table that was changed. Key schema names have the format _connector-name_._database-schema-name_._table-name_.`Key`. In this example: + 
   
   * `server1` is the name of the connector that generated this event. + 
  
positive.code: 
  Following is an example of what a message looks like:
  
  [source,json,indent=0,subs="attributes"]
  ----
  {
    "before": null,
  
negative.code: 
  ==== Decimal values
  
  [cols="30%a,17%a,53%a",options="header"]
  |===
  |SQL Server data type
  |Literal type (schema type)
  |Semantic type (schema name)
  
  |`NUMERIC[(P[,S])]`
  |`BYTES`
  |`org.apache.kafka.connect.data.Decimal` 
  
  |`DECIMAL[(P[,S])]`
  |`BYTES`
  |`org.apache.kafka.connect.data.Decimal` 
  
  |`SMALLMONEY`
  |`BYTES`
  |`org.apache.kafka.connect.data.Decimal`
  
  |`MONEY`
  |`BYTES`
  |`org.apache.kafka.connect.data.Decimal`
  
  |===
  
  The `scale` schema parameter contains an integer that represents how many digits the decimal point was shifted.
  The `connect.decimal.precision` schema parameter contains an integer that represents the precision of the given decimal value.
  
  [[sqlserver-deploying-a-connector]]
  == Deployment
  