DBZ-7359 Move documentation to connector specific page
This commit is contained in:
parent
90b734c170
commit
93458ccaf8
@ -107,6 +107,7 @@ Christian Stein
|
||||
Christopher Burch
|
||||
Christopher Sang
|
||||
Chuck Ha
|
||||
Ciaran O'Reilly
|
||||
Claus Guttesen
|
||||
Claus Ibsen
|
||||
Clément Loiselet
|
||||
|
@ -2999,7 +2999,7 @@ endif::product[]
|
||||
|[[mysql-property-database-jdbc-driver]]<<mysql-property-database-jdbc-driver, `+database.jdbc.driver+`>>
|
||||
|com.mysql.cj.jdbc.Driver
|
||||
|The driver class name to use. This can be useful when using an alternative driver to the one packaged with the connector.
|
||||
For information about how to connect {prodhame} to MariaDB, see xref:mysql-mariadb-support[Using the connector with a MariaDB database].
|
||||
For information about how to connect {prodname} to MariaDB, see xref:mysql-mariadb-support[Using the connector with a MariaDB database].
|
||||
|
||||
ifdef::product[]
|
||||
[IMPORTANT]
|
||||
|
@ -404,6 +404,16 @@ include::{partialsdir}/modules/all-connectors/con-connector-ad-hoc-snapshots.ado
|
||||
[id="sqlserver-incremental-snapshots"]
|
||||
=== Incremental snapshots
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
*SQL Server collations*
|
||||
|
||||
When SQL Server is configured with a collation whose sorting is not compatible with unicode's sorting algorithm (i.e. https://learn.microsoft.com/en-us/sql/relational-databases/collations/collation-and-unicode-support?view=sql-server-ver16#SQL-collations[SQL_* collations]) it is possible for data to be skipped when an adhoc snapshot is run.
|
||||
This can happen when the primary key column(s) are character based, not unicode, and the connection property `sendStringParametersAsUnicode` default value of `true` is used.
|
||||
To ensure records are not missed, disable sending string parameters as unicode by setting the value of the `database.sendStringParametersAsUnicode` property in connector configuration to `false`.
|
||||
Debezium follows the recommendations in SQL Server's https://learn.microsoft.com/en-us/sql/connect/jdbc/setting-the-connection-properties?view=sql-server-ver16[setting connection properties] documentation about this property, so that unicode and non-unicode columns are supported when it is set to `false`.
|
||||
====
|
||||
|
||||
include::{partialsdir}/modules/all-connectors/con-connector-incremental-snapshot.adoc[leveloffset=+1]
|
||||
|
||||
[WARNING]
|
||||
|
@ -77,18 +77,6 @@ endif::[]
|
||||
|
||||
|===
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
*SQL Server collations*
|
||||
|
||||
When SQL Server is configured with a collation whose sorting is not compatible with unicode's sorting algorithm (i.e. https://learn.microsoft.com/en-us/sql/relational-databases/collations/collation-and-unicode-support?view=sql-server-ver16#SQL-collations[SQL_* collations]) it is possible for data to be skipped when an adhoc snapshot is run.
|
||||
This can happen when the primary key column(s) are character based, not unicode, and the connection property `sendStringParametersAsUnicode` default value of `true` is used.
|
||||
|
||||
To ensure records are not missed, disable sending string parameters as unicode by setting the value of the `database.sendStringParametersAsUnicode` property in connector configuration to `false`.
|
||||
Debezium follows the recommendations in SQL Server's https://learn.microsoft.com/en-us/sql/connect/jdbc/setting-the-connection-properties?view=sql-server-ver16[setting connection properties] documentation about this property, so that unicode and non-unicode columns are supported when it is set to `false`.
|
||||
|
||||
====
|
||||
|
||||
.Triggering an ad hoc incremental snapshot
|
||||
|
||||
You initiate an ad hoc incremental snapshot by adding an entry with the `execute-snapshot` signal type to the signaling {data-collection}.
|
||||
|
Loading…
Reference in New Issue
Block a user