chore: Bump the dependencies group with 1 update

[dependabot]

Updated Microsoft.Data.SqlClient from 6.0.2 to 6.1.0.

Release notes

Sourced from Microsoft.Data.SqlClient's releases.

6.1.0

Release Notes

Stable Release 6.1.0 - 2025-07-25

This update brings the following changes since the
6.0.2 stable 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:

• Support for targeting .NET Standard 2.0 has returned.
  (#​3381)
• Support had previously been removed in the 6.0 release, with the
  community voicing concerns.
  ... (truncated)

6.1.0-preview2

Preview Release 6.1.0-preview2.25178.5 - 2025-06-27

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:

• Support for targeting .NET Standard 2.0 has returned. (#​3381)
• Support had previously been removed in the 6.0 release, with the [community voicing concerns] (Microsoft.Data.SqlClient 6.0 and .Net Standard dotnet/SqlClient#3115).

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:

... (truncated)

6.1.0-preview1

This update brings the following changes over the previous release:

Added

• Added packet multiplexing support to improve large data read performance. #​2714 #​3161 #​3202
• Added support for special casing with Fabric endpoints. #​3084

Fixed

• Fixed distributed transactions to be preserved during pooled connection resets. #​3019.
• Fixed application crash when the Data Source parameter begins with a comma. #​3250.
• Resolved synonym count discrepancies in debug mode. #​3098.
• Addressed warnings for down-level SSL/TLS versions. #​3126.

Changed

• Optimized binary size for AOT. #​3091
• Refined bulk copy operations to handle unmatched column names more effectively. #​3205.
• Enhanced SqlBulkCopy to explicitly identify mismatched column names. #​3183.
• Optimized outgoing SSPI blob handling using IBufferWriter<byte>. #​2452.
• Replaced byte[] with string for SNI to improve efficiency. #​2790.
• Code cleanup to remove SQL 2000 support #​2839, #​3206, #​3217,
• Connection pool design refactor for a modular connection pool design #​3199
• Updated various dependencies #​3229, primarily:
  • System.Text.Encodings.Web to v8.0.0
  • System.Text.Json to v8.0.5
  • Azure.Identity to v1.13.2
  • Microsoft.Identity.Model.Json.Web.Tokens to v7.7.1
  • Microsoft.Identity.Model.Protocols.OpenIdConnect to v7.7.1
• Code merge towards a unified SqlClient project, aligning .NET Framework and .NET Core implementations. (#​2957, #​2963, #​2984, #​2982, #​3023, #​3015, #​2967, #​3164, #​3163, #​3171, #​3182, #​3179, #​3156, #​3213, #​3232, #​3236, #​3231, #​3241, #​3246, #​3247, #​3222, #​3255, #​3254, #​3259, #​3264, #​3256, #​3251, #​3275, #​3277, #​3263, #​3292, #​3208).
• Test improvements include updates to test references, removal of hardcoded certificates, improved stability, and better coverage (#​3041, #​3034, #​3130, #​3128, #​3181, #​3060, #​3184, #​3033, #​3186, #​3025, #​3230, #​3237, #​3059, #​3061).

New Contributors

• @​emmanuel-ferdman made their first contribution in Update DockerLinuxTest/Program.cs reference dotnet/SqlClient#3041
• @​MaceWindu made their first contribution in Fix typo in Update 6.0.0-preview1.md dotnet/SqlClient#3134
• @​JNjenga made their first contribution in SqlBulkCopy: Explicitly state column name that mismatches(#3170) dotnet/SqlClient#3183
• @​Midhunnnk made their first contribution in Fix crash when Data Source starts with a comma dotnet/SqlClient#3250

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[JaCraig]

Approving this pull request because it includes a patch or minor update