-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when attempting to use Azure SQL database within an elastic pool as source for CDC based replication #6339
Comments
Hi @gavindew we use the Lines 175 to 188 in 6d9ba02
|
Hi @marcosmarxm. The database is an Azure Sql database, not a Azure Sql Managed Instance. Azure Sql databases do not support the USE keyword. For servers not supporting that USE statement, you need to specify the database before connecting. You can determine if you are running on Azure SQL vs Azure SQL Managed Instance using the ServerProperty('Edition') or ServerProperty('EngineEdition'). My suggestion would be if you are running on Azure SQL, you know you will always be in the correct database already (as you have no access to master) and so you can skip the USE statement. |
This requires further investigation before we decided that MS SQL connector cannot be used for Azure. Could be a simple fix. |
@alexandr-shegeda @kimerinn looks like the change which fixed this issue was reverted. Is this issue still fixed or should it be reopened now? |
Even though the changeling mentions the fix, it's not actually fixed.
|
What is the version of MS SQL Source connector that you are using? |
I'm using the latest version, 0.4.13 - it failed on 0.4.12 and 0.4.8 as well. Which is to be expected, as the fix mentioned above was reverted as soon as it was merged. |
@grishick is there a version I can switch to that works? |
@creativedutchmen today I used MS SQL Source connector version 0.4.16 with Airbyte to run a CDC sync from Azure SQL to BigQuery. I followed this tutorial to enable CDC on Azure SQL: https://www.mssqltips.com/sqlservertip/7237/azure-sql-database-change-data-capture-configuration-query-data/ |
Enviroment
Current Behavior
Fails on save with the error:
Could not connect with provided configuration. Error: com.microsoft.sqlserver.jdbc.SQLServerException: USE statement is not supported to switch between databases. Use a new connection to connect to a different database.
Expected Behavior
Should validate the database and save the source.
The database is configured for CDC and size is > S3 standard so CDC is supported and enabled.
Steps to Reproduce
The text was updated successfully, but these errors were encountered: