Fix SQL Server connection string #7079
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
The newer SQL Server ADO.NET drivers do not accept "asynchronous processing" as a parameter as it's on by default and cannot be changed.
|
The fix is to remove the parameter from the connection string. It seem to be that also some whitespace was removed, if this is a problem, let's see how to fix them back (arguably better like this?). :) |
|
The failures seem to be timeouts from code that is unrelated to the connectionstring change. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The newer SQL Server ADO.NET drivers do not accept
"asynchronous processing" as a parameter as it's on
by default and cannot be changed.