-
Bug
-
Resolution: Done
-
Major
-
2.0.0.Beta1
-
None
-
False
-
None
-
False
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
Debezium 2.0.0.Beta1
What is the connector configuration?
"connector.class": "io.debezium.connector.sqlserver.SqlServerConnector", "database.hostname": "<server>", "database.port": "1433", "database.user": "${file:/secrets/dev.properties:user}", "database.password": "${file:/secrets/dev.properties:password}", "database.server.name": "<server>", "database.names": "test-db", "table.include.list": "dbo.Payments,dbo.Step_FeePayments", "snapshot.mode": "schema_only", "database.history.kafka.topic": "db-events-history", "transforms": "Reroute,flatten,ValueToKey", "transforms.Reroute.type": "io.debezium.transforms.ByLogicalTableRouter", "transforms.Reroute.topic.regex": ".*", "transforms.Reroute.topic.replacement": "db-events", "transforms.flatten.type": "org.apache.kafka.connect.transforms.Flatten$Value", "transforms.flatten.delimiter": ".", "transforms.ValueToKey.type": "org.apache.kafka.connect.transforms.ValueToKey", "transforms.ValueToKey.fields": "source.db", "topic.creation.default.replication.factor": 1, "topic.creation.default.partitions": 10, "database.history.kafka.bootstrap.servers": "<bootstrap server>", "database.history.consumer.security.protocol": "SASL_SSL", "database.history.consumer.ssl.endpoint.identification.algorithm": "https", "database.history.consumer.sasl.mechanism": "PLAIN", "database.history.consumer.sasl.jaas.config": "${file:/secrets/dev.properties:confluentAuth}", "database.history.producer.security.protocol": "SASL_SSL", "database.history.producer.ssl.endpoint.identification.algorithm": "https", "database.history.producer.sasl.mechanism": "PLAIN", "database.history.producer.sasl.jaas.config": "${file:/secrets/dev.properties:confluentAuth}", "value.convertor": "org.apache.kafka.connect.json.JsonConverter", "value.converter.schemas.enable": "false"
What is the captured database version and mode of depoyment?
Microsoft SQL Azure (RTM) - 12.0.2000.8
What behaviour do you expect?
Debezium 2.0.0.Beta1 to connect with either single or multiple `database.names` listed.
What behaviour do you see?
Debezium will perform a check to see if CDC is enabled. The query it's attempting to perform `EXEC db.sys.sp_cdc_help_change_data_capture` this is not a valid query in Azure SQL. This causes the server to fail the check and Debezium to not connect.
Do you see the same behaviour using the latest relesead Debezium version?
Yes it is in the most recent 2.0.0.Beta1. Debezium currently works with 1.9.5.Final using Azure SQL.
