anchor.diff:  
   [cols="15%a,15%a,35%a,35%a",width=100,options="header,footer",role="table table-bordered table-striped"]
   |=======================
  -|PostgreSQL Data Type
  +|SQL Server Data Type
   |Literal type (schema type)
   |Semantic type (schema name)
   |Notes
  
positive.code: 
  |=======================
  
  [[timestamp-values]]
  ===== Timestamp values
  
  
negative.code: Fully-qualified names for columns are of the form _schemaName_._tableName_._columnName_.
  Note that primary key columns are always included in the event's key, also if blacklisted from the value.
  
  |`time.precision.mode`
  |`adaptive`
  | Time, date, and timestamps can be represented with different kinds of precision, including: `adaptive` (the default) captures the time and timestamp values exactly as in the database using either millisecond, microsecond, or nanosecond precision values based on the database column's type; or `connect` always represents time and timestamp values using Kafka Connect's built-in representations for Time, Date, and Timestamp, which uses millisecond precision regardless of the database columns' precision. See link:#temporal-values[temporal values].
  
  |`tombstones.on.delete` +
  0.10.0 and later
  |`true`
  