DBZ JDBC Sink support for MS SQL Server 2016

136 views

Skip to first unread message

CCHsu

unread,

Dec 18, 2023, 7:26:25 AM12/18/23

to debezium

Hi, Team,

Recently I try DBZ JDBC Sink v2.4 with MS SQL Server 2016 as target, but find that it failed with CURRENT_TIMEZONE() issue (error message appeared in the Kafka connect log).

SQL Error: 195, SQLSTATE: S0010 (org.hibernate.engine.spi.SqlExceptionHelper:133)
'CURRENT_TIMEZONE' is not a recognized built-in function name (org.hibernate.engine.spi.SqlExceptionHelper:138)

And I find that in the documentation the only supported SQL Server version is 2017 and 2019.

https://debezium.io/releases/2.4/#compatibility

I try to dig into the source code and only find the relevant part below.

https://github.com/debezium/debezium-connector-jdbc/blob/2.4/src/main/java/io/debezium/connector/jdbc/dialect/GeneralDatabaseDialect.java#L111

https://github.com/debezium/debezium-connector-jdbc/blob/2.4/src/main/java/io/debezium/connector/jdbc/dialect/sqlserver/SqlServerDatabaseDialect.java#L83

Although Confluent JDBC Sink works with SQL Server 2016, but I feel that it is better to use DBZ JDBC Sink for coherent integration.

Is the above timezone check functionality the only obstacle that causes DBZ JDBC Sink to work with SQL Server 2016?

Is it possible to extend the support of DBZ JDBC SInk to MS SQL Server 2016?

Best Regards.

Mario Fiore Vitale

unread,

Dec 19, 2023, 4:09:05 AM12/19/23

to debezium

Hi,

unfortunately we officially support MSSQL Server 2017 and 2019.

For this particular issue maybe you can try to define the CURRENT_TIMEZONE function by your own.

> Is the above timezone check functionality the only obstacle that causes DBZ JDBC Sink to work with SQL Server 2016?

Maybe yes, but I am not sure.

> Is it possible to extend the support of DBZ JDBC SInk to MS SQL Server 2016?

Let's see if the suggested workaround works and no other issue comes out.

thanks,