SQL Source Control - 3.0
Committing changes - SQL Source Control
Committing a change updates source control with that change.
When you make changes to a database that is linked to source control, SQL Source Control highlights affected objects in the Object Explorer:
To update source control with your changes, click the Commit Changes tab:

The Commit Changes tab lists all the objects in your database that anyone has made changes to.
To commit changes:
- Select the objects you want to commit.
- Optionally type or paste a comment.
- Click Commit
A progress dialog box is displayed while SQL Source Control commits the changes to your source control system.
Click OK to close the dialog box.
Source control is updated with your changes.
You can also commit changes by right-clicking an object, folder, or database in the Object Explorer, and clicking Commit changes to source control. The Commit Changes tab is displayed. The objects you clicked selected to commit.
Integrating with bug tracking systems
SQL Source Control enables you to integrate your database changes with a bug or issue tracking system (for example Jira, or FogBugz), or the project management features of Team Foundation Server. It does this by letting you associate a commit with an SVN bug ID or TFS work item.
For more information, see: Using SVN Bug IDs & TFS Work Items
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


Step by step examples