debezium / debezium/dbz

microsoft sql server connection url Windows VM with sql server [DBZ-1580]

Open
#264 0 comments 0 reactions 0 assignees View on GitHub
component/sqlserver-connector migrated-from-jira type/enhancement
Dominant language
HTML
Stars
6
Forks
8
Avg merge
2d 19h
Merged PRs (30d)
1

Description

Migrated from [DBZ-1580](https://issues.redhat.com/browse/DBZ-1580)

I am trying to test the debezium microsoft sql server source connector on Azure and it seems to work on a direct managed sql server bij connecting to ip address of the managed sql server on azure. But we are also using an mssql server on windows VM deployed which is deployed on azure. Within the VM we are running mssql (exact software is using this mssql). The normal connection string to connect to this mssql is to connect to the ip of the windows VM (IP: x.x.x.x) and use the so called instanceName to connect the the sql server inside the VM (instanName=EXACT....) . So the string is having a format like this:
hostname\InstanceName' (x.x.x.x\EXACT...). In some JDBC connectors the are using an extra parameter (JDBC Additional parameters) to add the instanceName to the 'connection.url'. My question would be is the debezium connector also having the to add extra parameters, like connection.addtionalParameters ?

Contributor guide

Open the contributing guide

Research direction

Review the Debezium Microsoft SQL Server source connector's connection.url handling and the requested instanceName or additional-parameter configuration. Reproduce the hostname\\InstanceName connection against SQL Server on an Azure Windows VM, then verify whether the connector can establish the connection and document the supported behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, sql
Domain
cloud, database
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.