anchor.diff:  |[[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. +
  - +
  -Supported values are: +
  -`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.
  +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`
  
positive.code: |
  | Timezone of the server.
  
  This is used to define the timezone of the transaction timestamp (ts_ms) retrieved from the server (which is actually not zoned). Default value is unset. Should only be specified when running on SQL Server 2014 or older and using different timezones for the database server and the JVM running the {prodname} connector. +
  When unset, default behavior is to use the timezone of the VM running the {prodname} connector. In this case, when running on on SQL Server 2014 or older and using different timezones on server and the connector, incorrect ts_ms values may be produced. +
  Possible values include "Z", "UTC", offset values like "+02:00", short zone ids like "CET", and long zone ids like "Europe/Paris".
  
  
negative.code: When the connector creates a snapshot, it completes the following tasks:
  
  1. Determines the tables to be captured.
  2. Obtains a lock on the SQL Server tables for which CDC is enabled to prevent structural changes from occurring during creation of the snapshot.
  The level of the lock is determined by `snapshot.isolation.mode` configuration option.
  3. Reads the maximum log sequence number (LSN) position in the server's transaction log.
  4. Captures the structure of all relevant tables.
  5. Releases the locks obtained in Step 2, if necessary. In most cases, locks are held for only a short period of time.
  6. Scans the SQL Server source tables and schemas to be captured based on the LSN position that was read in Step 3, generates a `READ` event for each row in the table, and writes the events to the Kafka topic for the table.
  7. Records the successful completion of the snapshot in the connector offsets.
  
  The resulting initial snapshot captures the current state of each row in the tables that are enabled for CDC.
  From this baseline state, the connector captures subsequent changes as they occur. 
  
  // Type: concept
  // ModuleID: how-the-debezium-sql-server-connector-reads-change-data-tables
  