Understand Toad Connections
Review this topic to learn about open database connections in Toad.
For information about switching the current connection in Toad, see Switching 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
- 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
- Select Tools | Options | Editor | General.
-
Clear the checkbox for the Use individual connection for each open editor option.
-
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:
- (DB2 and Oracle only) If your database supports executing multiple queries simultaneously on a shared connection, the query is placed in a queue and executes as soon as the current operation completes.
- 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.
Troubleshoot SQL Server Connections
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 |
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
By default, this file is located in the following directory: C:\Program Files\Quest Software\Toad Data Point version \Templates\Scripts Note: Clicking |
| 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:
|
| 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. |
may result in a "Path not found error". If you receive this error, manually enter the location in the field.
Understand
Determine the Best Method to Locate Objects
Toad offers a number of features to assist you in locating objects. The following table provides guidelines based on typical use cases:
|
If you know the.... |
Use this... |
|---|---|
|
Column name, but do not know the table name |
Use Object Search |
|
String of DDL for an object | |
|
Dependency for an object |
Uses and Used By tabs in the Database Explorer, and then drill-down to the object from there |
|
Criteria for excluding objects |
Filter feature in the Object Explorer |