SQL Source Control 3

Git, Mercurial, or other systems

SQL Source Control only has full integration with SVN, TFS and Vault.

If you want to link to another source control system, including Git or Mercurial, you can do this by:

  • linking to a working folder, or
  • linking to a custom setup using config files

Linking to a working folder

When you link to a working folder, SQL Source Control doesn't automate any source control operations (eg add, push, edit etc). Instead:

  • When you make changes to the database, the changes are listed in the Commit tab. When you click Save changes, the changes are scripted as SQL files to the working folder. You can then commit the script files manually with your source control client.
  • When the SQL files in your working folder are changed (eg by pulling with your source control system), the changes are listed in the Get latest tab. When you click Apply changes, the changes are applied to your database.

For instructions for how to link to Git, Mercurial or other source control system using a working folder, see Linking to a working folder.

If you want to do atomic commits of your database schema together with your application code, you can do this by linking to a working folder. For more information, see Example - source-controlling database schema and application code together using a working folder.

Linking to a custom setup

When you link to a custom setup, you specify a config file to automate source control operations. Preset config files are provided for:

  • Git
  • Mercurial
  • Perforce
  • Plastic SCM

For instructions for how to link to Git, Mercurial or other source control system with a custom setup, see Linking to a custom setup.

For more information about customizing config files, including how to create your own, see Working with config files.

Didn't find what you were looking for?