Bump dbup-sqlserver and Microsoft.Data.SqlClient

[dependabot]

Updated dbup-sqlserver from 5.0.37 to 7.2.0.

Release notes

Sourced from dbup-sqlserver's releases.

7.2.0

What's Changed

• Accept a Func instead of a pre-created connection by @​droyad in Accept a Func<SqlConnection> instead of a pre-created connection DbUp/dbup-sqlserver#34

Full Changelog: DbUp/dbup-sqlserver@7.1.0...7.2.0

7.1.0

What's Changed

• Breaking Change (only due to third party major version bump) Update Microsoft.Data.SqlClient from 5.2.2 to 6.1.2 by @​droyad in Update Microsoft.Data.SqlClient from 5.2.2 to 6.1.2 DbUp/dbup-sqlserver#27
• Allow use of an existing SQL Connection by @​droyad in Allow use of an existing SQL Connection DbUp/dbup-sqlserver#31
• Updated DbUp to 6.1.1 and patches to other libraries by @​droyad in Updated DbUp to 6.1.1 and patches to other libraries DbUp/dbup-sqlserver#30

Full Changelog: DbUp/dbup-sqlserver@6.0.16...7.1.0

6.0.16

What's Changed

• Use GenerateDocumentationFile to expose doc comments to package consumers by @​Bartleby2718 in Use GenerateDocumentationFile to expose doc comments to package consumers DbUp/dbup-sqlserver#25
• dbup-core v6.0.15 update by @​droyad in dbup-core v6.0.15 update DbUp/dbup-sqlserver#28

New Contributors

• @​Bartleby2718 made their first contribution in Use GenerateDocumentationFile to expose doc comments to package consumers DbUp/dbup-sqlserver#25

dbup-core changes: https://github.com/DbUp/DbUp/releases/tag/6.0.15
Full Changelog: DbUp/dbup-sqlserver@6.0.0...6.0.16

6.0.0

Breaking Changes

• Updated DbUp Core to 6.0.0, see https://dbup.readthedocs.io/en/latest/breaking-changes/ for full details
  • LibLog has been replaced by the standard .NET ILogger abstraction
    • The Autodetect logger feature provided by LibLog is removed
    • MultipleUpgradeLog has been replaced with AggregateLog
    • IUpgradeLogger still exists but method names have changed from Write* to Log* to match Microsoft's ILogger interface
  • Scripts with ScriptType.RunAlways will no longer be journaled
  • Only netstandard2.0 compatible frameworks are supported

• Update Azure SQL Authentication to use Azure.Identity by @​evochriso in Update Azure SQL Authentication to use Azure.Identity DbUp/dbup-sqlserver#14
• Replaced System.Data.SqlClient with Microsoft.Data.SqlClient

What's Else Has Changed

• Allow custom DB creation script to be passed by @​droyad in Allow custom DB creation script to be passed DbUp/dbup-sqlserver#20

New Contributors

• @​evochriso made their first contribution in Update Azure SQL Authentication to use Azure.Identity DbUp/dbup-sqlserver#14

Full Changelog: DbUp/dbup-sqlserver@5.0.41...6.0.0

6.0.0-beta.21

Full Changelog: DbUp/dbup-sqlserver@6.0.0-beta.9...6.0.0-beta.21

6.0.0-beta.9

What's Changed

• Updated DbUp Core to 6.0.0 by @​droyad in Updated DbUp Core to 6.0.0 DbUp/dbup-sqlserver#17

Full Changelog: https://github.com/DbUp/dbup-sqlserver/commits/6.0.0-beta.9

Commits viewable in compare view.

Updated Microsoft.Data.SqlClient from 6.1.3 to 6.1.4.

Release notes

Sourced from Microsoft.Data.SqlClient's releases.

6.1.4

This update brings the following changes since the 6.1.3 release:

Fixed

• Fixed NullReferenceException issue with SqlDataAdapter when processing batch scenarios where certain SQL RPC calls may not include system parameters.
  (#​3877)
• Fixed connection pooling issue where extra connection deactivation was causing active connection counts to go negative.
  (#​3776)

Added

AppContext Switch for enabling MultiSubnetFailover

What Changed:

• Added new AppContext switch Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault to set MultiSubnetFailover=true by default in connection string.
  (#​3851)

Who Benefits:

• Applications that need MultiSubnetFailover enabled globally without modifying connection strings.

Impact:

• Applications can now enable MultiSubnetFailover globally using one of the following methods:

// In application code
AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault", true);

// In runtimeconfig.json
{
  "configProperties": {
    "Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault": true
  }
}

<!-- In App.Config -->
<runtime>
  <AppContextSwitchOverrides value="Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault=true" />
</runtime>

Changed

• Optimized SqlStatistics execution timing by using Environment.TickCount instead of more expensive timing mechanisms.
  ... (truncated)

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[gunndabad]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.