|
Learn more about Toad for SQL Server Find solutions and downloads at the |
|
|
Learn more about Toad for SQL Server Find solutions and downloads at the |
| < To bookmark a page, right-click the Page Title and select Add to Favorites / Bookmark This Page |
Toad for SQL Server 5.7 |
For this release, the back-end of version control has been rewritten. If you previously used version control in Toad, the following may occur:
Review the following to help troubleshoot issues with version control:
| VSS Issues | Description |
|
Language support |
VSS 6.0 uses ANSI strings. Consequently, the English-encoded VSS server and client do not handle certain characters in other languages. This issue may also exist on previous or later VSS language installations. |
|
Case insensitive |
VSS is not case-sensitive. Using version control on objects whose names differ by case only can cause history and version-tracking issues. |
| CVS Issues | Description |
|
System cannot find file |
If a message stating that, “The system cannot find the file specified” displays, this usually means that the CVS executable cannot be found in the path you specified in the BinaryPath field of the Command Based Version Control Properties window. Verify that cvs.exe exists in the directory you specified in this field |
|
Command execution |
When executing CVS commands, user input is not allowed. This presents an issue when the user is using CVS with the SSH method and must enter a password to establish the Secure Shell. Workaround: Generate identity keys that automatically authenticate between the client and the server when connecting with SSH. |
| Subversion Issues | Description |
|
System cannot find file |
If a message stating that, “The system cannot find the file specified” displays, this usually means that the Subversion executable cannot be found in the path you specified in the BinaryPath field of the Command Based Version Control Properties window. Verify that svn.exe exists in the directory you specified in this field |
|
Command execution |
When executing Subversion commands, user input is not allowed. This presents an issue when the user is using Subversion with the SSH method and must enter a password to establish the Secure Shell. Workaround: Generate identity keys that automatically authenticate between the client and the server when connecting with SSH. |
| Object Issues | Description |
|
Adding multiple objects |
When you add multiple objects to version control, the objects are grouped and added in batches (for example, all the tables for a particular schema are added at once). If an error (for example, failure to support Korean characters) causes this command to fail, none of the objects are added. |
| Script Issues | Description |
|
Canceled check-in |
SQL scripts remain checked out if a change was made to the text, but check-in was canceled during the prompt for a check-in comment. This behavior is by design—that is; the user can either undo the checkout or check in the script Note: If you alter the object again, you receive a prompt to use the “locally changed” script. Click Yes to use the locally changed copy; click No to refresh the local copy from the source repository; click Cancel to cancel the prompt. |