SQL Source Control 4

SQL Source Control 3.4 release notes

3.4.10 - September 11th, 2013

Features

  • Subversion 1.8 support
  • Custom files for Git and Mercurial to allow committing changes with SQL Source Control

Fixes

  • Fix for TFS authentication issues [SOC-3630]

Known issues

3.4.9 - August 22nd, 2013 

Fixes

  • (SOC-5074) Fixed crashing tabs issue
  • Provided error message and workaround for "multiple .sqlproj files" error
  • No longer deletes commit comment on commit fail
  • Fixed bug where SQL Source Control ignores custom working base and transient location

3.4.8 - July 19th, 2013 

Fixes

  • Stability improvements

3.4.7 - July 18th, 2013 

Fixes

  • SOC-5084: Commit tab is no longer cut off when there are two lines of warning message
  • SOC-5055: fixed an issue that caused crashing when users deleted databases
  • Fixed SSMS2012 stability issues

3.4.6 - June 28th, 2013 

Fixes

  • SSMS no longer hangs when you restore databases
  • Crash when polling for changes introduced in 3.4.5

3.4.4 - June 12th, 2013 

Fixes

  • (SOC-4949, SQT-301) Fix for SSMS2012 crash when opening SQL Source Control tab hidden from view
  • Fix for comparison options appearing in Get latest list after unlinking and relinking

3.4.3 - June 7th, 2013 

Fixes

  •  (SOC-4927) Fixed blue notification icons appearing when there are no changes

3.4.2 - May 28th, 2013 

Feature

  • Much more responsive when selecting/deselecting thousands of objects simultaneously the Commit and Get latest tabs

Fixes

  • Fix for ".sqlproj is out of date" error when using SQL Server Database Projects
  • Fix for some users unable to launch SQL Compare Pro from the History dialog box

Known issues

3.4.1 - May 17th, 2013

Feature

  • Added customized options to link a database to Git, Mercurial, or a working folder.

Known issues

3.4.0 - May 10th, 2013 

Features

  • Allowed naming of migration scripts
  • Improved performance when refreshing the Commit or Get latest tabs

Known issues

  • Some combinations of TFS libraries on the client machine cause policy checking to fail, even if the policy requirements are met. For a workaround, add #ignorepolicies to your commit comment.

Didn't find what you were looking for?