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: (unless an explicit column value had been given), so there should rarely be the need to obtain the default value from the schema.
  Passing the default value helps though with satisfying the compatibility rules when xref:configuration/avro.advoc[using Avro] as serialization format together with the Confluent schema registry.
  
  ==== Temporal values
  
  [cols="20%a,15%a,30%a,35%a",width=150,options="header,footer",role="table table-bordered table-striped"]
  |=======================
  
negative.code: 
  |=======================
  
  When the `time.precision.mode` configuration property is set to `connect`, then the connector will use the predefined Kafka Connect logical types. This may be useful when consumers only know about the built-in Kafka Connect logical types and are unable to handle variable-precision time values. On the other hand, since SQL Server supports tenth of microsecond precision, the events generated by a connector with the `connect` time precision mode will *result in a loss of precision* when the database column has a _fractional second precision_ value greater than 3:
  
  [cols="20%a,15%a,30%a,35%a",width=150,options="header,footer",role="table table-bordered table-striped"]
  |=======================
  |SQL Server Data Type
  |Literal type (schema type)
  |Semantic type (schema name)
  |Notes
  
  |`DATE`
  |`INT32`
  |`org.apache.kafka.connect.data.Date`
  | Represents the number of days since epoch.
  
  |`TIME([P])`
  |`INT64`
  |`org.apache.kafka.connect.data.Time`
  | Represents the number of milliseconds since midnight, and does not include timezone information. SQL Server allows `P` to be in the range 0-7 to store up to tenth of microsecond precision, though this mode results in a loss of precision when `P` > 3.
  
  |`DATETIME`
  |`INT64`
  |`org.apache.kafka.connect.data.Timestamp`
  | Represents the number of milliseconds since epoch, and does not include timezone information.
  
  |`SMALLDATETIME`
  |`INT64`
  |`org.apache.kafka.connect.data.Timestamp`
  | Represents the number of milliseconds past epoch, and does not include timezone information.
  
  |`DATETIME2`
  |`INT64`
  |`org.apache.kafka.connect.data.Timestamp`
  | Represents the number of milliseconds since epoch, and does not include timezone information. SQL Server allows `P` to be in the range 0-7 to store up to tenth of microsecond precision, though this mode results in a loss of precision when `P` > 3.
  
  |=======================
  
  [[timestamp-values]]
  ===== Timestamp values
  
  