Linking to a custom setup
Published 16 July 2015
SQL Source Control has full integration with Git, SVN, TFS and Vault. If you want to use a different source control system (eg Mercurial), you can use 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
Before you link
The preset config files work well for most setups. However, if you want to use your own config file, create the file before you link.
For more information about how to create your own config file, see Working with config files.
To link to a custom setup
These instructions apply to SQL Source Control 4.1 and later.
- Create an empty folder in your source control repository. This will be the working folder you link to.
- In the Object Explorer, select the database you want to link to source control.
- In SQL Source Control, on the Setup tab, make sure Link to my source control system is selected and click Next:
On the Choose your source control system page, select Other and click Next.
The Link Database to Source Control dialog box opens:
Enter the location of the working folder.
Select the config file for your source control system.
If you're linking to a database that will be used by multiple developers, make sure Shared database is selected. For more information, see Database development models.
- Click Link.
The database is linked to source control. The database icon in the Object Explorer changes to show that the database is linked:
After you link
If you're the first person to link this database, add the database objects to source control. To do this, go to the Commit changes tab and commit the objects.
If you linked a database that's already in source control, update your database to the latest version. To do this, go to the Get latest tab and get the changes.
