Support Named Instances for Microsoft Sql Server #204
Merged
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
|
Great work! Thank you! |
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.
Microsoft Sql Server has what are known as named instances. These use dynamic ports and are connected to using the following syntax
AdventureWorks\myInstanceNamewhereAdventureWorksis the server name andmyInstanceNameis the instance name.The
tediouslibrary handles adding named instances to the connection config options throughoptions.instanceName. This notes that port and instanceName are mutually exclusive (as the port is dynamic when using named instances).This PR resolves this missing functionality by splitting the server into a server and instanceName and setting the port to undefined if the instanceName is present.