-
Notifications
You must be signed in to change notification settings - Fork 291
Upgrade Sql Client to 4.1.1 #924
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
Conversation
ConfigGenerators/MsSqlCommands.txt
Outdated
| @@ -1,4 +1,4 @@ | |||
| init --config "dab-config.MsSql.json" --database-type mssql --connection-string "Server=tcp:127.0.0.1,1433;Persist Security Info=False;User ID=sa;Password=REPLACEME;MultipleActiveResultSets=False;Connection Timeout=5;" --host-mode Development --authenticate-devmode-requests false --cors-origin "http://localhost:5000" | |||
| init --config "dab-config.MsSql.json" --database-type mssql --connection-string "Server=tcp:127.0.0.1,1433;Persist Security Info=False;User ID=sa;Password=REPLACEME;MultipleActiveResultSets=False;Connection Timeout=5;Encrypt=False;" --host-mode Development --authenticate-devmode-requests false --cors-origin "http://localhost:5000" | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reason for this change? perhaps accidental?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
trying to debug the connection issue that mssql was having after the update. Found an article that indicated the problem may be 4.0+ defaulting to encryption. The solution for that problem is to add this Encrypt=False to the connection string, which works fine locally for me as well, but is breaking the ConfigGenerator.sh script.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For MsSql Integration tests, the value specified in this file does not matter. The FileTransformTask that runs before the integration test replaces it with the value set in the pipeline variable. Adding Encrypt=False to the pipeline variable could be worth a try.
seantleonard
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let me know if any other changes occur so i can review/approve.
.pipelines/mssql-pipelines.yml
Outdated
| condition: eq( variables['Agent.OS'], 'Linux' ) | ||
| displayName: Get and Start Ubuntu SQL Server Image Docker | ||
| env: | ||
| DockerSQLpass: foo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe DockerSQLpass is also a pipeline variable that can be set when you set the connection string. Let's try setting both in the pipeline variables. We should not harcode the password in the yml.
…ub.com/Azure/hawaii-gql into dev/aaronburtle/UpdateSqlClientVersion
|
I see a PR: Upgrading Sql CLient to 5.0.1, |
Once I confirm I can get 5.0.1 working I will close this, otherwise, we will use 4.1.1 as a temporary fix. |
Why make this change?
Closes #911
Sql Client 3.0 is out of support, so we upgrade to 4.1.1
What is this change?
In
Directory.Build.Propswe change the Sql Version to 4.1.1How was this tested?
Ran against current test suite.
Sample Request(s)
Start and run engine as normal.