Chat now with support
Chat with Support

Toad for SQL Server 6.8.1 - Installation Guide

Create and Troubleshoot Connections

Understand Toad Connections

Review this topic to learn about open database connections in Toad.

Toad Open Connections

In Toad, an open connection in the Connection/Navigation Manager represents one or more actual connections to the database. When you open a database connection in Toad:

  • Toad creates an initial database connection for general use.
  • Toad also creates a separate database connection for each Editor (the first time you execute a statement) and for each Data tab in the Database Explorer (the first time you select the tab and query data).

    The connection associated with the window (or tab) remains open until you close the window. If a window has an associated connection, but a statement is not currently executing, the connection is in an inactive state.

To view information for an open connection

  • To view the number of actual database connections that exist for a Toad connection, including the number of active connections, place the cursor over the connection in the Connection/Navigation Manager pane or in the connection drop-down list.

To use the Background Processes pane

  • When a statement is executing, a progress bar displays in the Status bar located at the bottom of the Toad application window. Click the executing progress bar to open the Background Processes pane.
  • To cancel statement execution, use the Background Processes pane.

    Note: It is recommended that you cancel only your own processes, because terminating Toad activities could cause unexpected behavior.

Sharing a Connection Among Windows

You can instruct Toad to share an open connection among windows. In this way, the Editor windows and Data tabs can share the same connection when the connection is inactive.

To share a database connection among windows in Toad

  1. Select Tools | Options | Editor | General.
  2. Clear the checkbox for the Use individual connection for each open editor option.

  3. When this option is not selected, Toad attempts to use a single connection for any new windows or query execution. For example, if you share a database connection, you can execute a query in the Editor, execute another query in a new Editor, and then select the Data tab from the same connection.

    If the single connection is in use when Toad attempts to execute it, the following occurs:

    • If your database does not support executing multiple queries on a shared connection, a dialog prompts you to either permanently associate the window with a new database connection, cancel the previous operation, or add the query to a queue until the current operation completes, and the execute it. If you place multiple queries in the queue, each one executes in the order that it was added to the queue.

Note: Although you can share a database connection, any commits apply to the selected window only.

Create SQL Server Connections

You can create a new connection, or connect to an existing connection from the Create New Connection window. See Troubleshoot SQL Server® Issues for more information about troubleshooting connection issues.

Note: For SQL Azure connections:

  • To be able to utilize majority of Toad functionality please grant VIEW DEFINITION on the SQL Azure databases you want to work with.
  • You can login to Windows Azure Platform by selecting Tools | Cloud Computing | SQL Azure Portal and providing your credentials.
  • Make sure that no Azure firewall rule restricts your IP address from having access to Azure server. See "Create and Alter Azure Firewall Rules" in the online help for more information.

To create a new connection

  1. Click on the toolbar (ALT+F+N).

  1. Select SQL Server from the Group list box.
  2. Review the following for additional information:

    Login Tab Description

    Server name

    Enter the name of the server to use when connecting.

    Click to display any servers running SQL Server that are currently active on the network.


    • For SQL Azure connections, enter in this field.
    • For named instances, enter the MachineName\InstanceName in this field.


    Select the type of authentication to use for this connection.

    Note: You cannot create a SQL Azure connection using Windows Authentication.


    Enter the password to use when connecting.

    Tip: After connecting, you can set a master password to further secure your connection in Tools | Options| Environment | Security.


    Select or create a category if you want to color code Editor tabs for a specific connection. This can help differentiate between development and production databases. You can also set an option to color code the Object Explorer pane and object editor windows (Create, Alter, Drop, etc.).   Click here to view a video of this feature.

    Encrypt connection

    Select this option to enable encryption for the current connection provided that the certificate has been already installed on the server.
    Advanced Tab Description

    Network protocol

    Select one of the following:

    • Shared Memory
    • TCP/IP
    • Named Pipes

      Note: When establishing Named Pipes connection "Poll service status in connection list" option should be cleared.

    Parameter Name/Value

    You can add parameters to the connection. Toad includes the Application Name parameter with value Toad for SQL Server by default.
  1. Click Connect to save the connection and immediately connect to the database.


    Click Save to save the connection without connecting to the database.  

Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help | About.

To import connections (including Central Management Server connections)

  1. Click .
  2. Specify the location where the connections currently reside.

    Note: Review the following for additional information on CMS connections:

    • To import CMS connections, select a server from the list where the CMS is registered. The connection to this SQL Server instance should be created beforehand.
    • CMS is available beginning with Microsoft SQL Server 2008.
    • User should have an appropriate login (Windows Authentication and grant to connect to selected server are required) created on the server to which he connects via CMS.
  3. Select the connections to be imported.

Troubleshoot SQL Server Issues

Installation Issues

The following table describes issues related to installing Toad.

Issue Cause/Solution

When installing Toad on Windows 7 64-bit, Program Compatibility Assistant may appear with “This program might not have installed correctly” message.


Select This program installed correctly to continue installation. For more information, see

Toad Plug-in for Microsoft® SQL Server Management Studio Issues

Issue Cause/Solution

Toad Plug-in cannot be invoked from Microsoft SQL Server Management Studio after you uninstalled one of several editions of Toad that resided on your machine side-by-side.

If you have several editions of Toad for SQL Server installed side-by-side (for example, Beta, Trial and Commercial) and you uninstall one of them, Toad Plug-in files are removed as a part of un-installation process.


Select one of the following:

  • Reinstall Toad for SQL Server. All current settings will be available after Toad reinstallation.
  • Launch SsmsInstallation.exe from the Windows command prompt as administrator.
    1. Open SSMS Installation directory (<Toad install directory>/ SSMS Installation) from the Windows command prompt.
    2. Enter the following:

      SsmsInstallation.exe [Type of Product/Mode] "[TSS Installation Directory]"


      [Type of Product/Mode] can be Uninstall, Freeware, Beta, Commercial, Trial

      [TSS Installation Directory] is the directory where Toad for SQL Server resides.


    C:\Program Files (x86)\Quest Software\Toad for SQL Server 6.8\SSMS Installation\SsmsInstallation.exe Commercial "C:\Program Files (x86)\Quest Software\Toad for SQL Server 6.8"

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.


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:




For example:,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.


To enable remote connections, see "How to configure SQL Server 2005 to allow remote connections" at:

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


"Could not find a part of the path
C:\Program Files\Quest Software
\Toad for SQL Server\Template\Scripts\
" 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.


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 for SQL Server 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.


  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.


  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" in the online help 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 Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating