Update from System.Data.SqlClient to Microsoft.Data.SqlClient

[cheenamalhotra]

Summary of the new feature / enhancement

It seems PowerShell SDK continues to be dependent on System.Data.SqlClient, which is obsolete and is not recommended by the driver community since many years now.

Ref: https://devblogs.microsoft.com/dotnet/introducing-the-new-microsoftdatasqlclient/

Microsoft.Data.SqlClient is the new driver library that must be used instead.
Use Porting Cheat Sheet to port application.

Could you elaborate why that migration hasn't been made in PowerShell SDK yet or if this is planned in near future?

Proposed technical implementation details (optional)

No response

[iSazonov]

See #16156 (comment)

@SteveL-MSFT What WG could make a conclusion about the Travis's comment?

[rhubarb-geek-nz]

I have done some investigation and packaging the new Microsoft.Data.SqlClient in PowerShell itself is problematic.

It contains a large number of dlls that simply aren't needed if you are not using it, and also includes its own copy of Azure.Core.dll and Azure.Identity.dll. These have potential to conflict with other modules and deployments.

A far better solution is to leave it to PSGallery and load the dlls in an AssemblyLoadContext.

I have a proof of concept on github and PSGallery

[SteveL-MSFT]

@daxian-dbw do you know why the SDK is dependent on this assembly? Looking in the source, I don't see any actual usage of it unless something else PowerShell depends on is depending on it?