dbForge Source Control is a convenient SSMS add-in for SQL Server database change management in all the popular version control systems and servers. The tool can be embedded into the database DevOps to automate SQL changes management.

Version-control database schemas and static table data
Use either dedicated or shared development models
Commit and revert changes with dependency awareness
View conflicts and resolve data and schema inconsistencies visually
Track changes and detect who, when, and why made them
Plug Source Control directly into SQL Server Management Studio
Automate database development with the DevOps approach

Supported Source Control Systems
dbForge Source Control supports all the major version control systems, including Azure DevOps Server (previously known as Team Foundation Server a.k.a. TFS), Apache Subversion (SVN), TFVC, Git (including GitHub, GitLab, and Bitbucket), Mercurial (Hg), Perforce (P4), SourceGear Vault.

The tool helps version-control database schemas and data, view and resolve conflicts, rollback changes, and maintain the overall integrity of databases. With dbForge Source Control, you will deploy your databases safely without losing data.

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.

Only for V.I.P