Skip to content

Conversation

@aaronburtle
Copy link
Contributor

@aaronburtle aaronburtle commented Oct 28, 2022

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.Props we change the Sql Version to 4.1.1

How was this tested?

Ran against current test suite.

Sample Request(s)

Start and run engine as normal.

@@ -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"
Copy link
Collaborator

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?

Copy link
Contributor Author

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.

Copy link
Contributor

@severussundar severussundar Oct 31, 2022

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.

Copy link
Contributor

@seantleonard seantleonard left a 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.

condition: eq( variables['Agent.OS'], 'Linux' )
displayName: Get and Start Ubuntu SQL Server Image Docker
env:
DockerSQLpass: foo
Copy link
Collaborator

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.

@abhishekkumams
Copy link
Contributor

I see a PR: Upgrading Sql CLient to 5.0.1,
then if this PR is not required. it should be closed.

@aaronburtle
Copy link
Contributor Author

aaronburtle commented Dec 9, 2022

I see a PR: Upgrading Sql CLient to 5.0.1, then if this PR is not required. it should be closed.

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.

@aaronburtle aaronburtle changed the title Upgrade Sql Client to 4.1.0 Upgrade Sql Client to 4.1.1 Dec 9, 2022
@aaronburtle aaronburtle closed this Dec 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consider using a supported version of the SQL Server driver

6 participants