https://linen.dev logo
Join Slack
Powered by
Hi, has anyone here ever tried to use an Azure SQL...
# replication-troubleshooting
n
Hi, has anyone here ever tried to use an Azure SQL Managed Instance as a source? My managed instance has a public endpoint configured, which allows me to connect to it from SSMS, but Airbyte gives me a non-json response error when trying to set it up as a source. Edit: So the connection works when I select "Standard" as the replication method, but fails when I choose CDC. I have CDC enabled on the database and all the tables in it, and SQL server agent is running.
m
Which version of Airbyte are you using?
n
@Marcelo Pio de Castro 
0.40.24
m
The "non-json error" is a problem with airbyte-proxy, it was fixed on Airbyte 0.40.26, can you try updating?
n
I will try to update and see. Also to clarify on my original post, I am actually getting 
Could not connect with provided configuration. Error: Index 0 out of bounds for length 0
, not the non-json response error.
@Marcelo Pio de Castro I upgraded and am still getting 
Could not connect with provided configuration. Error: Index 0 out of bounds for length 0
m
Which tier of Azure SQL are you using? It is required to be S3+ to use CDC
n
It's a managed instance, which supports CDC. I have it enabled at the db level and the table level, enabled snapshot isolation as well.
m
Can you post the log of a retest of the source?
n
where can I find the log?
m
It should be generated after you click on the retest button on the Source
Oh, this is the server logs, it is not that, you can get it directly from the Source UI. Or you can get it from the logs of the worker: 
docker-compose logs worker
n
it looks like it doesn't have permission to run the command to check the status of sql server agent
it looks like the connector code may not account for azure managed instance
m
Yeah, I think you can open an issue for that
n
5 Views
Open in Slack
PreviousNext
Powered by