anchor.diff:  
   |5
   |`ts_ms`
  -a|Optional field that displays the time at which the connector processed the event. The time is based on the system clock in the JVM running the Kafka Connect task.  +
  +a| Optional field that displays the time at which the connector processed the event. 
  +In the event message envelope, the time is based on the system clock in the JVM running the Kafka Connect task. +
    +
  -In the `source` object, `ts_ms` indicates the time that the change was made in the database. By comparing the value for `payload.source.ts_ms` with the value for `payload.ts_ms`, you can determine the lag between the source database update and {prodname}.
  +In the `source` object, `ts_ms` indicates the time that the change was made in the database. 
  +By comparing the value for `payload.source.ts_ms` with the value for `payload.ts_ms`, you can determine the lag between the source database update and {prodname}.
   
   |===
   
  
positive.code: 
  |[[sqlserver-property-source-timestamp-mode]]<<sqlserver-property-source-timestamp-mode, `source.timestamp{zwsp}.mode`>>
  |_commit_
  |String representing the criteria of the attached timestamp within the source record (ts_ms).
  `commit` will set the source timestamp to the instant where the record was committed in the database (default and current behavior).
  `processing` will set the source timestamp to the instant where the record was processed by {prodname}. This option could be used when either we want to set the top level `ts_ms` value here or when we want to skip the query to extract the timestamp of that LSN.
  
  |[[sqlserver-property-event-processing-failure-handling-mode]]<<sqlserver-property-event-processing-failure-handling-mode, `event.processing{zwsp}.failure.handling{zwsp}.mode`>>
  |`fail`
  
negative.code: |[[sqlserver-property-snapshot-mode]]<<sqlserver-property-snapshot-mode, `snapshot.mode`>>
  |_initial_
  |A mode for taking an initial snapshot of the structure and optionally data of captured tables.
  Once the snapshot is complete, the connector will continue reading change events from the database's redo logs. 
  The following values are supported: 
  
  * `initial`: Takes a snapshot of structure and data of captured tables; useful if topics should be populated with a complete representation of the data from the captured tables. +
  * `initial_only`: Takes a snapshot of structure and data like `initial` but instead does not transition into streaming changes once the snapshot has completed. +
  * `schema_only`: Takes a snapshot of the structure of captured tables only; useful if only changes happening from now onwards should be propagated to topics.
  
  |[[sqlserver-property-snapshot-include-collection-list]]<<sqlserver-property-snapshot-include-collection-list, `snapshot.include.collection.list`>>
  | All tables specified in `table.include.list`
  