SQL Source Control - 2.1
Learning SQL Source Control - 2.1
Linking a database to source control
Linking is the setup step for SQL Source Control. You need to link before you can commit the database objects.
Linking:
- associates a database with a location in source control, allowing SQL Source Control to monitor changes
- lets you tell SQL Source Control if a database is shared, so it can alert you to any conflicts or issues with shared working
For more information, see Database development models
When linking a database, you have two options:
- Link the database to source control
This is used to source control a database for the first time; to associate your version of a database with one that is already source controlled; or to get a new database from source control.
- Use the evaluation repository
This creates a local Subversion repository on your computer, so you can evaluate SQL Source Control even if you do not have source control set up.
For more information, see Using the evaluation repository
To link a database to source control:
- In SQL Source Control, on the Setup tab, ensure a database is selected, and click Link to source control.
The Link Database to Source Control dialog box is displayed:

- On the left hand side, select your source control system; either Subversion (SVN), Team Foundation Server (TFS) or Just Evaluating.
- Provide details for the source control location you want to link the database to.
For Subversion:
Type or paste the URL for your Subversion repository.
If you are creating a new link, you need to specify an existing, empty folder in your Subversion repository. SQL Source Control does not create the folder for you.
For Team Foundation Server:
Type or paste the URL of your Team Foundation Server and the port number to connect to that server; type or browse to the location of the Team Project and solution you want to associate with the database.
If you are creating a new link you need to specify the location of an existing, empty source control folder. You are recommended to create a new folder. SQL Source Control does not create it for you.
- Tell SQL Source Control if the database is shared.
If you are linking to a database that will be used by multiple developers, ensure the This is a shared database radio button 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:

Note that linking only associates the database with a location in source control.
If you are creating a new link, the database objects are not yet source controlled.
If you are linking to an existing version, your database has not yet been updated to that version.
To commit the objects or get the latest version, next go to either the Commit Changes tab or the Get Latest tab.
See also |
Was this article helpful?
SQL Source Control
- Setting SQL Compare options within SQL Source Control
- "ICredentialsProvider is unset, therefore can't get" error occurring within SQL Source Control
- Linking fails due to SVN pre-commit hooks
- Logging changes to shared databases
- Object changed by Unknown
- Setting permissions for SQL Source Control
- Using SQL Source Control with Team Foundation Server 2012 or tfspreview.com
- Error: Failed to resolve no-ops after 5 tries
- Using SQL Compare or SQL Changeset scripts with SQL Source Control
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SQL Source Control
- Database development models
- Release notes - version 1.0
- Release notes - version 1.1
- Release notes - version 2.0
- Release notes - version 2.1
- Release notes - version 2.2
- Requirements & prerequisites
- Technical Overview
- Release notes - version 3.0
all SQL products
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs

Using SQL Source Control
Working with source control systems