version control

Having a database under source control brings huge benefits. Therefore, we decided to review and compare two popular version control tools, dbForge Source Control add-in for SSMS and Visual Studio Version Control, to help you pick a tool that meets your needs best.

This is the fifth part of an extensive article dedicated to database versioning. Before you proceed with it, we suggest that you read the previous parts:

• Part I: Version Control with Git
• Part II: Database Versioning with Examples
• Parts III & IV: Database Version Control Using Source Control for SQL Server

There are many solutions for version-controlling databases. We are going to review one of them, namely Source Control which comes in the SQL Tools pack. As an example, we will use the JobEmplDB database for a recruitment service:

Version-controlling SQL Server databases in GitHub has never been easier with Devart solutions. You can commit and revert changes, view and resolve conflicts, track changes and link static data with convenience. And such tools as dbForge Source Control will help you easily and effectively manage your GitHub repository.

But now let’s go back and see where it all begins. Let’s see how to create a new repo on GitHub and then clone it to your local computer.

To properly manage the database development process, stay informed of the changes delivered by other developers, and avoid conflicts or missing data in the database, one needs database versioning. This allows you to reconstruct any version of the database, view the history of changes, and ensure smooth database delivery.

The article deals with the basics of versioning SQL Server databases and goes into the basics of working with the Git version control system.