Skip to content

Update dependency Microsoft.Data.SqlClient to 6.1.1 #951

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 25, 2025

This PR contains the following updates:

Package Change Age Confidence
Microsoft.Data.SqlClient (source) 6.0.1 -> 6.1.1 age confidence

Release Notes

dotnet/sqlclient (Microsoft.Data.SqlClient)

v6.1.1

This update includes the following changes since the 6.1.0 release:

Fixed
  • Reverted changes related to improving partial packet detection, fixup, and replay functionality. This revert addresses regressions introduced in 6.1.0. (#​3556)
  • Applied reference assembly corrections supporting vector, fixed JSON tests, and ensured related tests are enabled. #​3562
  • Fixed SqlVector<T>.Null API signature in Reference assembly. #​3521
Changed
  • Upgraded Azure.Identity and other dependencies to newer versions. (#​3538) (#​3552)

v6.1.0

This update brings the following changes since the
6.1.0-preview2 release:

Added

No new features were added.

Fixed
  • Fixed missing socket error codes on non-Windows platforms.
    (#​3475)
  • Fixed primary/secondary server SPN handling during SSPI negotiation.
    (#​3478)
  • Fixed AzureKeyVaultProvider package key caching to serialize Azure key fetch
    operations.
    (#​3477)
  • Fixed a rare error related to multi-packet async text reads.
    (#​3474)
  • Fixed some spelling errors in the API docs.
    (#​3500)
  • Fixed a rare multi-packet string corruption bug.
    (#​3513)
Changed
SqlDecimal type workarounds conversions

What Changed:

  • Changed how SqlDecimal type workarounds perform conversions to meet
    compliance policies.
    (#​3467)

Who Benefits:

  • Microsoft products must not use undocumented APIs on other Microsoft products.
    This change removes calls to undocumented APIs and replaces them with
    compliant API use.

Impact:

  • These changes impose an observed 5% decrease in performance on .NET Framework.
SqlVector API improvements

What Changed:

  • Several changes were made to the SqlVector API published in the
    6.1.0-preview2 release
    (#​3472):
    • The SqlVector class was changed to a readonly struct.
    • The null value constructor was changed to a static CreateNull() method.
    • The Size property was removed.

Who Benefits:

  • SqlVector instances gain the efficiencies of struct handling.

Impact:

  • Early-adopter applications may require updates if they rely on the old APIs
    and any class-specific behaviour.

v6.0.2

This update brings the following changes since the
6.1.0-preview1 release:

Added
Added dedicated SQL Server vector datatype support

What Changed:

  • Optimized vector communications between MDS and SQL Server 2025, employing a
    custom binary format over the TDS protocol.
    (#​3433,
    #​3443)
  • Reduced processing load compared to existing JSON-based vector support.
  • Initial support for 32-bit single-precision floating point vectors.

Who Benefits:

  • Applications moving large vector data sets will see beneficial improvements
    to processing times and memory requirements.
  • Vector-specific APIs are ready to support future numeric representations with
    a consistent look-and-feel.

Impact:

  • Reduced transmission and processing times for vector operations versus JSON
    using SQL Server 2025 preview:
    • Reads: 50x improvement
    • Writes: 3.3x improvement
    • Bulk Copy: 19x improvement
    • (Observed with vector column of max 1998 size, and 10,000 records for each
      operation.)
  • Improved memory footprint due to the elimination of JSON
    serialization/deserialization and string representation bloat.
  • For backwards compatibility with earlier SQL Server Vector implementations,
    applications may continue to use JSON strings to send/receive vector data,
    although they will not see any of the performance improvements noted above.
Revived .NET Standard 2.0 target support

What Changed:

Who Benefits:

  • Libraries that depend on MDS may seamlessly target any of the following
    frameworks:
    • .NET Standard 2.0
    • .NET Framework 4.6.2 and above
    • .NET 8.0
    • .NET 9.0
  • Applications should continue to target runtimes.
    • The MDS .NET Standard 2.0 target framework support does not include an
      actual implementation, and cannot be used with a runtime.
    • An application's build/publish process should always pick the appropriate
      MDS .NET/.NET Framework runtime implementation.
    • Custom build/publish actions that incorrectly try to deploy the MDS .NET
      Standard 2.0 reference DLL at runtime are not supported.

Impact:

  • Libraries targeting .NET Standard 2.0 will no longer receive warnings like
    this:
    • warning NU1701: Package 'Microsoft.Data.SqlClient 6.0.2' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.
Fixed
  • Fixed missing <NeutralLanguage> property.
    (#​3325)
  • Fixed injection of UTF-8 BOM during bulk copy.
    (#​3399)
  • Fixed SqlCachedBuffer async read edge case.
    (#​3329)
  • Fixed SqlSequentialTextReader edge case with single-byte reads.
    (#​3383)
  • Fixed an incorrect error message when parsing connection string PoolBlockingPeriod.
    (#​3411)
  • Added missing ToString() override to SqlJson.
    (#​3427)
Changed

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file. label Apr 25, 2025
@renovate renovate bot force-pushed the renovate/microsoft.data.sqlclient-6.x branch from 07d6227 to 2004175 Compare July 25, 2025 21:52
@renovate renovate bot changed the title Update dependency Microsoft.Data.SqlClient to 6.0.2 Update dependency Microsoft.Data.SqlClient to 6.1.0 Jul 25, 2025
@renovate renovate bot force-pushed the renovate/microsoft.data.sqlclient-6.x branch from 2004175 to 76f1e68 Compare August 5, 2025 01:44
@renovate renovate bot changed the title Update dependency Microsoft.Data.SqlClient to 6.1.0 Update dependency Microsoft.Data.SqlClient to 6.0.2 Aug 5, 2025
@renovate renovate bot changed the title Update dependency Microsoft.Data.SqlClient to 6.0.2 Update dependency Microsoft.Data.SqlClient to 6.1.1 Aug 15, 2025
@renovate renovate bot force-pushed the renovate/microsoft.data.sqlclient-6.x branch from 76f1e68 to 829e5e5 Compare August 15, 2025 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants