Learn more about Toad for SQL Server
at Quest.com

Find solutions and downloads at the
Toad for SQL Server Support Portal

< To bookmark a page, right-click the Page Title and select Add to Favorites / Bookmark This Page

Toad for SQL Server 5.7

You are here: Manage Connections > Understand Toad Connections

Understand Toad Connections

In Toad, a connection represents one or more actual connections to the database. Toad creates an initial database connection for general usage. It also creates a separate database connection for each Editor (the first time you execute a statement) and a separate database connection for each Data tab in the Database Explorer (the first time you select the tab and data is queried). The database connection for each Editor and Data tab remain open until you close the associated window; however, the connections remain in an inactive state if a statement is not currently executing.

Tips:

To view the number of actual database connections that exist for a Toad connection and how many of those database connections are active, place the cursor over the connection in the Connection Manager or the Connection toolbar.
You can view the progress of statements executing in the background in a progress bar located on the lower right side of the status bar. To cancel a script's execution, click the progress bar to display the Background Processes window. See Stop Background Processes for more information.It is recommended to cancel only your own processes, as terminating Toad activities may lead to unexpected behavior.

Share Database Connections

Editors and Data tabs can share the same database connection when the connection is inactive if you clear the Use specific connection for each open editor checkbox in Tools | Options | Editor | General. Any new executions or windows attempt to use this connection first. 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 connection is in use and you attempt to execute it, one of 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.