Skip to content
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

Fix | Fix issue connecting with instance name from Unix environment #870

Merged
merged 1 commit into from Jan 12, 2021

Conversation

cheenamalhotra
Copy link
Member

Fixes #868

@cheenamalhotra cheenamalhotra added this to In Progress in SqlClient v3.0 via automation Jan 7, 2021
@cheenamalhotra cheenamalhotra added this to the 3.0.0-preview1 milestone Jan 7, 2021
SqlClient v3.0 automation moved this from In Progress to Reviewer Approved Jan 8, 2021
@cheenamalhotra cheenamalhotra merged commit 45a6696 into dotnet:master Jan 12, 2021
SqlClient v3.0 automation moved this from Reviewer Approved to Done Jan 12, 2021
@Crono1981
Copy link

Just to add on this: if the server only has named instances, then any attempt at opening a connection will throw an exception.

My understanding is that this happens because in resolving "address\instance", the targeted data source becomes in fact "address", which would then point to a non-existing Sql Server. The fix should therefore cover this case too.

Is my assumption correct?

@cheenamalhotra
Copy link
Member Author

Yes, that's correct!
We're also backporting this to v2.1 (PR #874) for next patch release.

@Crono1981
Copy link

Thanks for the blazing fast reply, @cheenamalhotra ! I am happy to hear I will not have to wait until v3 for this fix. 😁

Keep up the good work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

The instance name is ignored when running on Linux
5 participants