dbForge Source Control for SQL Server
Features Overview

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.

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.

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.

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.