Converse agora com nosso suporte
Chat com o suporte

Toad Data Point 5.5 - Installation Guide

Troubleshoot SQL Server Issues

Connection Issues

Review the following solutions to help troubleshoot SQL Server connection issues in Toad.

Issue Cause/Solution

Cannot specify a port number when connecting

Currently, Toad does not have a separate field for specifying a port number.

Solution:

You can connect if you know the port number for the instance by entering the following in the Server name field on the New Connection window:

ServerName,Port

or

IPAddress,Port

For example:   

10.1.29.129,1234 (where 1234 is the port number of the instance) 

Cannot connect to a remote instance in SQL Server 2005

Remote connections may not be enabled in SQL Server 2005. Also, named instances are configured to use dynamic ports and select an available port once the SQL Server Service starts. If you are connecting to a named instance through a firewall, configure the Database Engine to listen on a specific port, so that the appropriate port is opened in the firewall.

Note: Remote connections are disabled by default in the Express and Developer editions of SQL Server 2005.

Solution:

To enable remote connections, see "How to configure SQL Server 2005 to allow remote connections" at: http://support.microsoft.com/kb/914277

"Path is not of a legal form" error message when connecting

or

"Could not find a part of the path
C:\Program Files\Quest Software
\Toad Data Point\Template\Scripts\
InitialSqlServer.Sql
" error message when connecting

You attempted to migrate settings from a previous install of Toad to the current install, but the settings file (InitialSqlServer.Sql) for the previous install was either removed, moved, or corrupt.

You may also receive this error if you installed Toad and migrated settings from a previous version, and later uninstalled the previous version.

Solution:

You must specify a valid location for the InitialSqlServer.Sql file in Toad.

To specify a valid location

  1. Open the SQL Server options page under Tools | Options | Database | SQL Server.

  2. Specify the location for the new install's InitialSqlServer.Sql file in the Run Script on new connection field.

By default, this file is located in the following directory:

C:\Program Files\Quest Software\Toad Data Point version \Templates\Scripts

Note: Clicking may result in a "Path not found error". If you receive this error, manually enter the location in the field.  

Cannot establish Named Pipes connection

If you are trying to connect to the server using Named Pipes, "Poll service status in connection list" option should be cleared.

Solution:

  1. Open the options page under Tools | Options | Database | General.
  2. Clear Poll service status in connection list checkbox.
Cannot establish Azure connection

Failing to establish Azure connection may indicate that your IP address is restricted from having access to the Azure server.

Solutions:

  1. Select Tools | Cloud Computing | SQL Azure Portal to login to Azure Portal.
  2. Create a firewall rule on the master database, enabling access to current IP address or range. See Create and Alter Azure Firewall Rules for more information.
Cannot access some functionality when working with Azure connection.

To utilize majority of Toad functionality VIEW DEFINITION grant is required for those databases you want to work with.

 

Related Topics

Create SQL Server Connections

Manage Connections

Connection/Navigation Manager 

Troubleshoot Sybase ASE Issues

Review the following solutions to help troubleshoot SAP issues pertaining to the following in Toad:

Connection Issues

Issue Cause/Solution

Unable to connect to the database. The following message displays: "The ODBCMDA procedures have not been installed on this database..."

Stored procedures that the ODBC driver requires currently do not exist on the server.

Solution:

Install the required procedures.

Missing Functionality or Object Information

Issue Cause/Solution

Unable to view or export data for objects with non-standard names.

The ASE ODBC driver has issues handling non-standard names for objects.

Solution:

When setting up an ASE connection in Toad, select Use quoted identifiers on the Connection tab in the Adaptive Server Enterprise window to enable the use of quotations in identifiers.

Unable to view linked tables.

Linked tables store DSN connection information.

Solution:

Set up the DSN connection information exactly the same on all machines that access the database.

Other Issues

Issue Cause/Solution

DBMS name showing as SQL Server.

Older versions of the ASE ODBC driver return SQL Server as the DBMS name.

Solution:

Upgrade to the latest version of the ODBC driver, which correctly returns Adaptive Server Enterprise as the DBMS name.

 

Related Topics

Create SAP Connections

Manage Connections

Connection/Navigation Manager 

Configure Version Control

File Version Control

Toad can integrate with your existing version control system allowing you to maintain multiple versions of Toad files. After you integrate Toad with your version control system, you can perform version control tasks directly from within Toad, such as commit file changes and retrieve revisions.

Toad supports the following version control systems for managing Toad files:

  • Apache Subversion™—Toad has been tested with Subversion 1.7.5 and 1.8.

The following types of files can be managed using version control from within Toad: Editor (.tef, .sql, .txt), Query Builder (.tsm), ER Diagram (.ter), and Automation (.tas).

To configure version control for Toad files

  1. Ensure that an Apache Subversion client is installed on the same computer as Toad.
  2. In Toad, open one of the supported file types. Then right-click the document window tab and select File Version Control | Version Control Wizard. This action opens the Version Control Wizard which allows you to configure Toad for your version control system.

  3. Use the wizard to provide information about your version control system to Toad. Review the following for additional information:

    Field/Button  
    Version Control System Page  

    Type

    Select Subversion.

    Properties

    Click the Properties button and enter the path to the Subversion executable (svn.exe) on the client computer. For example, if using TortoiseSVN, the path might be:

    C:\Program Files\TortoiseSVN\bin

    Note: Do not include svn.exe in the path.

    Server

    Enter the URL for the Subversion repository on the Subversion server.

    Login and Password

    Enter the user name and password for your Subversion account.
    Default Version Control Settings Page  

    Version Control Folder

    Select the folder on the Subversion server where you want to check in files.

    If you currently have files under version control, select the folder on the server where these files are located.

    Working Folder

    Select a folder on the client computer to use as the root working folder. This is the location into which you will check out files.

    If you currently have files under version control, select your existing working folder.

To add a file to version control

  1. After configuring version control for files, you can start adding files to version control from within Toad. Right-click a document window tab and select File Version Control | Add file to working folder.
  2. Select a location in your working folder in which to save the file. Click Save.
  3. In the Commit dialog, enter a comment and click OK to add the file to version control.

To browse the repository

  1. Right-click the document window tab (of one of the supported file types) and select File Version Control | Repository Browser.
  2. In the Repository Browser you can right-click a file to perform one of the following actions. Available actions depend on the file's status.

    Action Description
    Open Open the file in Toad.
    Commit Commit your changes. Available for Modified or Untracked files.
    Undo Changes Discards your changes and reverts to the previous revision of the file (previous commit). Available when the file status is Modified.
    Get Latest Version Check out the latest revision from the remote repository. Available when the file status is OutOfDate.

To commit your changes

  • After modifying a file, right-click the document window tab and select File Version Control | Commit.

To compare revisions (Editor files only)

  • After modifying and saving an Editor file, you might want to compare your changes to the remote copy (last commit) before committing your changes. Right-click the document tab and select File Version Control | Diff with latest revision.
  • You can compare two revisions of an Editor file (.tef, .sql, or .txt) by using the History dialog.
    1. To open a file's History dialog, right-click the document tab and select File Version Control | Show history.
    2. Select two revisions to compare. Then right-click the revisions and select Compare revisions.
    3. For an OutOfDate file, right-click the latest revision in the History dialog and select Compare with working copy to compare the remote file to your working copy.

To check file status

  • The status of a currently open file displays in the status bar of the document window. You can also place the cursor over the document tab to display status.
  • You can check the status of one or more files by using the Repository Browser. To update file status in the Repository Browser, right-click a folder and select Update folder.
  • Review the following file status definitions.

    File Status Definition
    Untracked The file has not been added to version control. Right-click the file in the Repository Browser and select Commit to add it to version control.
    UpToDate The file in your working folder is synchronized with the file in the remote repository. No changes are detected. No action is required.
    Modified The working copy of this file was modified. The changes are stored in the working folder only. Commit this file to add the changes to the remote repository.
    OutOfDate A more recent revision of this file exists in the remote repository. To update your working copy, check out the latest revision from the remote repository (right-click the file and select Get Latest Version).
    Unknown The file is under version control, but its status cannot be determined.
    Deleted The file was under version control, but it was dropped or renamed in the working folder and exists only in the remote repository.

Additional Actions

  • To open the folder where a file is located, open the file and then right-click the document tab and select File Version Control | Open in Windows Explorer.

 

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação