Release notes - version 2.2

SQL Source Control is an add-in for SQL Server Management Studio that allows you to source control your databases.

Note that SQL Source Control is not a source control system; it allows you to store your databases in your existing source control system.

This article discusses:

Features in version 2.2
Known issues in version 2.2
Bug reports and feedback
Getting more information

Features in version 2.2

Version 2.2 of SQL Source Control introduces the following new features:

Object filtering
If you want to exclude objects from SQL Source Control, you can set up filters so they are not shown on the Commit Changes or Get Latest tabs. This is useful, for example, if there is a specific set of objects you never want to commit to source control.

For more information, see Using filters to exclude objects
Repository browsing when linking
The Link To Source Control dialog box now includes a Browse button for Subversion, Team Foundation Server and Vault. Use this to browse your source control repository when you are linking to source control.

The browse functionality also lets you create new folders in your repository, so you can get set up without needing to leave SQL Server Management Studio.

Known issues in version 2.2

SQL Source Control version 2.2 has the following known issues:

Config files are no longer included for CVS and Bazaar

When linking a database to source control, on the Link to Source Control dialog box, presets are no longer included for the CVS and Bazaar source control systems.

You can still create a custom config file to support any source control system with a command line interface.

This change does not affect users who are already using CVS or Bazaar with SQL Source Control.

Performance issues when source controlling large quantities of data

If the data tables you are source controlling have a large number of rows, the Commit Changes and Get Latest tabs may be slow to populate and refresh.

Because performance can be poor for large quantities of source controlled data, you are recommended only to source control static (lookup) data.

Note that large quantities of data, or data that changes frequently (such as transactional data) should not be source controlled.

Bug reports and feedback

We are continuing to develop SQL Source Control, and we value any feedback you may have.

Please let us know about any issues you may encounter.

If SQL Source Control encounters a serious issue, you may see an error report dialog box:

Please click Send Error Report, and - if possible - provide detailed feedback, as these reports are extremely valuable to us.

These error reports may include:

a stack trace
your SQL Server and operating system version
the Windows user you are logged in as, and your domain
This is so we can identify recurrent bugs.
information from the SQL Source Control logs
In some conditions, this may include information about your database schema.

Getting more information

Was this article helpful?

Search support