dbForge Source Control for SQL Server
Features Overview

dbForge Source Control for SQL Server is a visual SSMS add-in with a simple-to-use interface that helps you easily keep track of what has been changed, when, and why in SQL Server database objects. The tool enables you to connect databases to multiple version control systems and servers, such as Azure DevOps Server (TFS), Apache Subversion (SVN), TFVC, Git (including GitHub, GitLab, and Bitbucket), Mercurial (Hg), Perforce (P4), and SourceGear Vault.

dbForge Source Control for SQL Server can be integrated into SSMS thus allowing you to manage changes and version-control code in a familiar interface.

Source-control databases: shared vs dedicated database development model

Maintain a clear source code by either working on your database copy or sharing a database with other team developers. You can select one of the following development models during the process of linking a database to source control:

  • Dedicated: Make changes to a local or cloned copy of the database. Then, commit and push them to a remote repository so that other developers can update their database copies.
  • Shared: Work on a single shared database and repository.
Learn more about database development models
Database development models

Version-control a SQL database working folder

dbForge Source Control enables you to source-control a SQL database working folder with a version control system in the way you version-control other files.

You can link the database to the working folder in the Link Database to Source Control dialog. In the Source control repository box, click Add and select Working folder from the dropdown list. Then, specify a path to the database folder, type a repository name, and click OK. Once linked, you can make an initial commit or pull the latest changes from the repository.

Learn more about the usage of the Source Control tool
Version-control a SQL database working folder

Manage database changes

In dbForge Source Control Manager, you can handle database changes as follows:

  • Commit: Save your changes to a source control repository.
  • Get Latest: Update your local copy of the database with the latest changes from the source control repository.
  • Undo: Revert your uncommitted changes to the database.
Learn more about how to version-control databases on GitHub
Change management

Resolve conflicts

If you face any conflicts, you can resolve a conflicted file between local and remote database copies in one of the following ways:

  • Get Local: Commit your changes to the database.
  • Get Remote: Override your local changes with the latest changes from the remote repository.
Learn some additional information about how to version-control with Git in Azure DevOps
Resolve conflicts

Version-control static data

To keep your database a proper structure, you can link and version-control SQL database schemas and static data. Static data is a fixed data set that is almost never changed after it has been collected. It may include geographical locations, reference data, lookup tables, etc.

With dbForge Source Control, you can link static data to a remote repository, view, commit or undo changes, get the latest changes, and resolve any conflicts, if any.

Learn more about how to version-control static data conflicts
Version-control static data

Undo uncommitted changes

You can undo the changes you have made locally and which have not been committed, and roll back the database to the earlier state. For example, these changes may include accidental deletion of database objects or unexpected behavior to which these changes may lead.

To undo the changes, in the Source Control Manager > Local Changes section, select the changes and click Undo.

Undo uncommitted changes

Track database changes

If you need to see who made a change, when, and why either of the database files, you can use the Changes History document. To access it, right-click the linked database and select Source Control > View Changes History.

In the document that opens, you can see the history of changes associated with the commit, view a list of objects that were altered in the commit, analyze DDL differences for each database object, and compare two revisions.

Learn more about changes history and other features of dbForge Source Control
Track database changes

Automate database development with the DevOps approach

Source Control as part of the DevOps workflow is aimed at optimizing and automating SQL Server database build development and maintaining database integrity.

After you made the changes to the local copy of the database, you can link the database with your changes to source control. After that, in Source Control Manager, select the changes you want to synchronize with the source control repository and commit them.

Learn more about Source Control as part of the DevOps process
Automate database development with the DevOps approach
Streamline all database tasks in SSMS with dbForge SQL Tools (including Source Control) Try now