anchor.diff:  * {LinkDebeziumInstallRHEL}[{NameDebeziumInstallRHEL}]
   endif::product[]
   
  +
  +// Type: concept
  +// ModuleID: debezium-sql-server-connector-configuration-example
  +// Title: {prodname} SQL Server connector configuration example
   [[sqlserver-example-configuration]]
  -=== Example configuration
  +==== Example configuration
   
   To use the connector to produce change events for a particular SQL Server database or cluster:
   
   . Enable the {link-prefix}:{link-sqlserver-connector}#setting-up-sqlserver[CDC on SQL Server] to publish the _CDC_ events in the database.
   . Create a configuration file for the SQL Server connector.
   
  -When the connector starts, it will grab a consistent snapshot of the schemas in your SQL Server database and start streaming changes, producing events for every inserted, updated, and deleted row.
  -You can also choose to produce events for a subset of the schemas and tables.
  -Optionally ignore, mask, or truncate columns that are sensitive, too large, or not needed.
  +When the connector starts, it will create a consistent snapshot of the schemas in your SQL Server database and start streaming changes, producing change event records for every row in which data was inserted, updated, or deleted.
  +Optionally, you can configure the connector to produce change events for a subset of the schemas and tables in a database.
  +For example you can ignore, mask, or truncate columns that contain sensitive data, that are larger than a specified size, or that you do not need.
   
   ifdef::community[]
   Following is an example of the configuration for a connector instance that monitors a SQL Server server at port 1433 on 192.168.99.100, which we logically name `fullfillment`.
  
positive.code: [[sqlserver-transaction-metadata]]
  === Transaction metadata
  
  {prodname} can generate events that represents tranaction boundaries and that enrich data change event messages.
  
  {prodname} generates events for every transaction `BEGIN` and `END`.
  Every event contains
  
  * `status` - `BEGIN` or `END`
  * `id` - string representation of unique transaction identifier
  * `event_count` (for `END` events) - total number of events emmitted by the transaction
  * `data_collections` (for `END` events) - an array of pairs of `data_collection` and `event_count` that provides number of events emitted by changes originating from given data collection
  
  Following is an example of what a message looks like:
  
  [source,json,indent=0,subs="+attributes"]
  ----
  {
  
negative.code: In the following example, a column `phone_number` is added to the `customers` table.
  
  . Type the following command to start the database shell:
  [source,shell]
  ----
  docker-compose -f docker-compose-sqlserver.yaml exec sqlserver bash -c '/opt/mssql-tools/bin/sqlcmd -U sa -P $SA_PASSWORD -d testDB'
  