How dbForge Source Control is involved in the DevOps process

Although the dbForge Source Control tool is not used in the Continuous Integration process directly, database developers do use version-controlling extensively in their work.

Naturally, a database is a critical part of an application. Thus, if the changes (e.g. the ones related to the delivery of a new app version to customers) do not find their way into the production database, the entire application may end up working improperly. Long story short, version-controlling is crucial for the entire database development lifecycle.

When implementing a new feature, or improving the current functionality, a developer normally deploys a local database on their machine, makes changes to the database schema objects, such as adding or modifying tables, columns, stored procedures, etc. The number of such changes may be quite huge and all of them are made right in the deployed database. Eventually, the time to save the changes to the database comes.

dbForge Source Control displays all the changes made to the database, and provides an option to review them prior to committing. The following example illustrates a case of database deployment from a script folder and putting it under source control to track changes made during a database schema change.

dbForge Source Control within SQL Databse Development
Right-click a database you want to put under source control, and select Link Database to Source Control option from the Source Control sub-menu.
Configure the settings in the Link Database to Source Control wizard.
dbForge Source Control - Link Database to Source Control wizard.
After the changes have been made to the database schema, you can view them and select the ones to be synchronized with the script folder.
After synchronization, the script folder will contain new changes. Later, they can be pushed to the source control server (Git or another).

Using dbForge Source Control when synchronizing with popular version control systems

The example above showed how to use the dbForge Source Control tool when synchronizing with the script folder. Generally, the tool allows you to link your database to the following version control systems:

  • Subversion (SVN)
  • Team Foundation Server (including TFS Cloud)
  • Git (including GitHub)
  • Perforce (P4)
  • Mercurial
  • SourceGear Vault
You can do this in the Link Database to Source Control wizard by configuring the necessary options.
When working with these data sources, users get an additional opportunity to view the history of changes on the server.


The dbForge Source Control tool is an essential assistant in the day-to-day database development. It takes only a few minutes to configure all the settings and link the database to one of the supported source control systems without having to break a workflow.

Learn about other dbForge tools involved in collaborative
database development and deployment