Skip to content
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

Add support for migrating from System.Data.SqlClient to Microsoft.Data.SqlClient #1593

Open
cheenamalhotra opened this issue Aug 8, 2024 · 0 comments
Labels
design-proposal label for issues that are design proposal Triaged Label to show that UA team has triaged this issue.

Comments

@cheenamalhotra
Copy link
Member

Summary

Microsoft.Data.SqlClient is the successor of System.Data.SqlClient, actively supported by Microsoft, while System.Data.SqlClient is in security maintenance mode.

Motivation and goals

MDS made it's entry in 2019 and has gained stability and customer adoption over the years.
The first introductory blog post is here: https://devblogs.microsoft.com/dotnet/introducing-the-new-microsoftdatasqlclient/

Porting to the new package involves namespace and package reference updates. More details can be found in porting-cheat-sheet.

In scope

Namespace changes, package reference updates, and everything mentioned in the porting cheat sheet linked above.

Out of scope

Functionality changes that need manual reviewing.

Risks / unknowns

  • An application may face database connectivity issues after migration due to insecure customer environment setups and enhanced security enabled by default by the new library. From security perspective, this is an acceptable risk and customers must be made aware of the functionality changes to help resolve connectivity issues.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-proposal label for issues that are design proposal Triaged Label to show that UA team has triaged this issue.
Projects
None yet
Development

No branches or pull requests

2 participants