Version Control Systems
You can use a version control system (VCS) in conjunction with Team Coding to control files and database objects. SQL Navigator provides direct support to specific third-party version control systems and it also provides SCC support to connect to additional version control systems. You must have Team Coding installed to work with a VCS through SQL Navigator.
|
|
Important: Quest Software is unable to provide support for source control issues caused by the version control system, including the version control system's support for Microsoft's SCC API. If you have problems connecting to Toad through SCC, contact the version control system's Support. |
Direct Supported
| Version Control System | Version | ||
|---|---|---|---|
| Concurrent Versions System (CVS)* |
CVS 1.11.9 and later CVSNT 2.08 and later For more information, see Concurrent Version (CVS) System Requirements. | ||
|
Git * |
A git client for Windows must be installed. | ||
|
IBM Rational ClearCase * |
Version 7.1 for Windows. ClearTool command line is required. For more information, see More about IBM Rational ClearCase and SQL Navigator.
| ||
|
Perforce * |
2010.2 (command-line client) For more information, see More about Perforce and SQL Navigator.
| ||
|
Serena PVCS * |
5.2 and later
Serena PVCS Version Manager:
| ||
|
Apache Subversion (SVN)* |
1.6.5 and later | ||
|
Microsoft Team Foundation Server |
2005 through 2013 For more information, see More about Team Foundation Server and SQL Navigator. | ||
|
Microsoft Visual SourceSafe |
5.0, 6.0, and 2005 (8.0) |
*These version control systems connect using a command-line client.
SCC Support
In addition to providing direct support to the version control systems, SQL Navigator supports additional version control systems through Microsoft's SCC API. You should be able to connect to any version control system that uses SCC.
To connect to a version control system using SCC, you must install the system's SCC-compliant client. See the system's documentation for instructions on how to install their SCC client.
|
|
Note: It is strongly recommended you use the native APIs for SourceSafe and PVCS when using Team Coding (instead of the SCC integration). Most version control systems that integrate with SQL Navigator through the SCC API ignore the "Force revision" flag and the "Create a new revision for existing objects" option when exporting. |