MS SQL Server: allow connections to datasource\namedInstance #256
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There used to be explicit check which forbids connection via dataSource = host\<instance name>. That seems to be working fine now so I'm removing this restriction.
benilovj
added a commit
that referenced
this pull request
Mar 22, 2014
…ring-support mssql: allow connect to to datasource\namedInstance
|
Separately from this change, what I've always wanted to do but never got around to was to document the different ways to build the connection string for SQL Server, like you described in the PR description. One question that comes up again and again on the forums is how to connect to SQL Server.... |
benilovj
changed the title
benilovj
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There used to be explicit check which forbids connection via dataSource =
host\<instance name>. That seems to be working fine now (tested with SQL Sever Express 2014) so I'm removing this restriction.Example connection definitions which work fine with named instances:
instanceName=...:Connection to named instance requires MS SQL Server Browser service to be up and running and allowed by firewalls (if any). Each database should be also configured to accept TCP/IP connections (including allowance in firewall if any).
This targets to fix #120