anchor.diff:  The transaction events are written to the topic named `<database.server.name>.transaction`.
   
   ==== Change data event enrichment
  -When transaction metadata is enabled the data message `Envelope` is enriched with a new `transaction` field.
  +When transaction metadata is enabled, the data message `Envelope` is enriched with a new `transaction` field.
   This field provides information about every event in the form of a composite of fields:
   
  -* `id` - string representation of unique transaction identifier
  -* `total_order` - the absolute position of the event among all events generated by the transaction
  -* `data_collection_order` - the per-data collection position of the event among all events that were emitted by the transaction
  -
  -Following is an example of what a message looks like:
  +`id`:: String representation of unique transaction identifier
  +`total_order`:: The absolute position of the event among all events generated by the transaction
  +`data_collection_order`:: The per-data collection position of the event among all events that were emitted by the transaction
  +
  +The following example shows what a typical message looks like:
   
   [source,json,indent=0,subs="+attributes"]
   ----
  
positive.code: toc::[]
  endif::community[]
  
  {prodname}'s SQL Server Connector can monitor and record the row-level changes in the schemas of a SQL Server database.
  
  The first time it connects to a SQL Server database/cluster, it reads a consistent snapshot of all of the schemas.
  When that snapshot is complete, the connector continuously streams the changes that were committed to SQL Server and generates corresponding insert, update and delete events.
  All of the events for each table are recorded in a separate Kafka topic, where they can be easily consumed by applications and services.
  
  // Type: concept
  // Title: Overview of {prodname} SQL Server connector 
  
negative.code: |[[sqlserver-property-max-batch-size]]<<sqlserver-property-max-batch-size, `max.batch.size`>>
  |`2048`
  |Positive integer value that specifies the maximum size of each batch of events that should be processed during each iteration of this connector. Defaults to 2048.
  
  |[[sqlserver-property-heartbeat-interval-ms]]<<sqlserver-property-heartbeat-interval-ms, `heartbeat.interval{zwsp}.ms`>>
  |`0`
  