SQL Source Control

Datenbankversionskontrolle in SSMS.

Veröffentlicht von Redgate Software
Wird von ComponentSource seit 2005 vertrieben

Version: 8.1.x NEU Letzte Aktualisierung: Apr 9, 2026

i

Please Note: SQL Source Control is no longer available as a standalone product for new purchases. It is only available for new license purchases as part of SQL Toolbelt Essentials or Flyway Teams.
If you already own existing licenses of this product, please contact us for pricing to add additional licenses to your existing license key.

SQL Source Control 5.8

Released: Aug 1, 2017

Updates in 5.8

Funktionen

  • Updated the comparison options dialog to display more information and allow searching for specific options.
  • Global Options are now available by clicking the 'Options' button in the header bar, rather than through the Setup tab. This means they are available even when you don't have a linked database selected.
  • All of the linking options (source control, working folder, and evaluation) now follow a consistent workflow.

Fehlerkorrekturen

  • Fixed an issue where SQL Source Control would fail to compare users if the domain was different.
  • Fixed a bug where for some machines database registration could fail with the message "An unexpected error was encountered while querying the database system tables..." (with the original error message "String was not recognized as a valid DateTime").
  • Fixed spurious TEXTIMAGE_ON clauses are no longer appended to tables with computed columns registered from scripts folders.
  • SQL Source Control now handles dependencies between fulltext indexes and other indexes correctly.
  • SSMS 2008 and SSMS 2008R2 are no longer supported.
  • SQL Source Control now requires .NET Framework version 4.6.1 or greater.
  • SQL Source Control will now correctly treat multiplication/division operations as having a higher precendence than bitwise operations when parsing SQL.
  • SQL Source Control can now write constraints with an AT TIME ZONE clause correctly.
  • SQL Source Control will no longer script out an empty ALTER SEQUENCE statement when the only extended properties are different between the respective sequences.