anchor.diff:  * `fulfillment.dbo.customers`
   * `fulfillment.dbo.orders`
   
  +If the default topic name do not meet your requirements, you can configure custom topic names.
  +To configure custom topic names, you specify regular expressions in the logical topic routing SMT. 
  +For more information about using the logical topic routing SMT to customize topic naming, see {link-prefix}:{link-topic-routing}#topic-routing[Topic routing].  
  +
  + 
   // Type: concept
   // ModuleID: how-the-debezium-SQL Server connector-uses-the-schema-change-topic
   // Title: How the {prodname} SQL Server connector uses the schema change topic
  
positive.code: === Topic names
  
  The SQL Server connector writes events for all `INSERT`, `UPDATE`, and `DELETE` operations for a specific table to a single Kafka topic. 
  By default, the names of the Kafka topics take the form _serverName_._schemaName_._tableName_.
  
  * _serverName_ is the logical name of the connector as specified with the `database.server.name` configuration property.
  * _schemaName_ is the name of the database schema where the operation occurred.
  * _tableName_ is the name of the database table in which the operation occurred.
  
  For example, suppose that `fulfillment` is the logical server name in the configuration for a connector that is capturing changes in a SQL Server installation.
  The server has an `inventory` database with the schema name `dbo`, and the database contains tables with the names `products`, `products_on_hand`, `customers`, and `orders`. 
  
negative.code: 
  [WARNING]
  ====
  The format of the messages that a connector emits to its schema change topic is in an incubating state and can change without notice.
  ====
  
  {prodname} emits a message to the schema change topic when the following events occur:
  