Documente Academic
Documente Profesional
Documente Cultură
Installation Guide
Copyright
Copyright 2
Contents 3
Installation 5
System Requirements 5
Client Requirements 5
Server Requirements 6
Virtualization Support 6
User Requirements 7
Install Toad 8
Specify Application Data Directory Location 8
Install Toad Silently 9
Silent Installation Using the Executable 9
Install Toad on Citrix® Systems 11
Upgrade Toad 12
Upgrade Automation Scripts and Scheduling Tasks 12
Upgrade Automation Scripts to Newer Version of Toad 12
Migrate Scheduling Tasks to Newer Version of Toad 13
Files Migrated During Upgrades 14
Integration between Toad and Microsoft SQL Server Management Studio 15
Install and Uninstall Toad Plug-In 16
Uninstall Toad 16
Create Connections 18
Understand Toad Connections 18
Toad Open Connections 18
Sharing a Connection Among Windows 18
Create SQL Server and SQL Azure Connections 19
Troubleshoot Connections 21
Troubleshoot SQL Server® Issues 21
Installation Issues 21
Toad Plug-in for Microsoft® SQL Server Management Studio Issues 21
Connection Issues 22
About Us 40
We are more than just a name 40
Our brand, our vision. Together. 40
Contact Quest 40
Technical Support Resources 40
Index 41
System Requirements
Review the following client and database server requirements for Toad® for SQL Server.
Client Requirements
Before installing Toad, ensure that your client system meets the following minimum hardware and software
requirements:
Requirement Details
Platform 2 GHz processor (recommended minimum)
Memory 4 GB of RAM minimum, 16 GB recommended
Note: The memory required may vary based on the following:
l Applications that are running on your system when using Toad
l Size and complexity of the database
l Amount of database activity
l Number of concurrent users accessing the database
Hard Disk 800 MB to install Toad
Space 104 MB to run Toad
Note: The disk space required may vary based on the edition of Toad selected for
installation.
Operating Windows Server® 2008 R2 SP2
System Windows Server® 2012
Windows Server® 2012 R2
Windows Server® 2016
Windows® 7 SP1 (32-bit or 64-bit)
Windows® 8.1 (32-bit or 64-bit)
Windows® 10 Anniversary Update
Windows® 10 Creators Update
Important: Toad uses the Microsoft® Distributed Transaction Coordinator (DTC) when
opening a SQL file to get Full-Text Search status, but DTC is disabled by default on
Windows Server 2008 and Windows 7. If you are using either operating system, ensure that
Network DTC access is enabled on the Toad client. See http://technet.microsoft.com/en-
us/library/cc753510(WS.10).aspx for more information about enabling DTC access.
.NET Microsoft® .NET Framework 4.7.1
Framework
Additional Web Browser
Server Requirements
Before installing Toad, ensure that your server meets the following minimum hardware and software
requirements:
Requirement Details
Database Server SQL Server 2005 (Service Pack 2 or later) and SQL Server 2005 Express
SQL Server 2008 and SQL Server 2008 Express
SQL Server 2008 R2 and SQL Server 2008 R2 Express
SQL Server 2012 and SQL Server 2012 Express
SQL Server 2014 Enterprise and SQL Server 2014 Express
SQL Server 2016
Notes:
l SQL Server Compact Edition is not supported.
l Storage Management is not available on SQL Server Express.
Cloud Database SQL Azure and Azure SQL Data Warehouse
Service Note: To be able to utilize a majority of Toad functionality, please grant VIEW
DEFINITION on the SQL Azure databases you want to work with.
Virtualization Support
Requirement Details
Application When deploying Toad in a virtualization environment, for best results ensure the
Virtualization system accurately reflects the applicable client hardware and software requirements
listed in this document.
Toad has been developed using Microsoft guidelines (see Remote Desktop Services
programming guidelines) and can be deployed and operated in virtualization
environments such as Citrix XenApp, Microsoft App-V, and VirtualBox.
See "Install Toad on Citrix® Systems" on page 11 for more information.
Server Toad has been tested with the following:
Virtualization
l Oracle VM 3.1 running on Red Hat Enterprise Linux 64-bit with Oracle 11gR2
l Oracle VM 2.2 running on Windows 2008 32-bit with Oracle 11gR2
To install Toad
1. Run the Installer.
2. Accept the License Agreement.
3. Select the products you want to install and click Install.
Note: When installing Toad using Quest Software Installer 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.
Note: Check Prohibit saving passwords during the installation to prohibit users from saving their
passwords in Toad.
Caution: All current Toad settings will be lost after applying this Registry setting unless you manually copy
the settings files from the default location (Roaming directory) to the new location (Local directory). Copy the
settings files BEFORE you add the Registry setting and BEFORE opening Toad.
You can customize MSIEXEC command-line options and overrides for your installation similar to the
following command:
“ToadInstaller.exe” /S /Lx “C:\temp\installLog.txt” INSTALLDIR=”Drive:\your_
install_path” USERNAME=”some_user” COMPANYNAME=”your_company” ALLUSERS=1
Use the following descriptions to customize the command-line options and overrides for your installation.
Option Description
/L “C:\temp\installLog.txt” (Optional) Write installation messages to the specified log file.
Substitute “C:\temp\installLog.txt” in the example with the fully qualified
name of the log file. Enclose this value in double quotations. The
installation process creates this file if it does not exist. Otherwise, the
existing file is overwritten.
You can add additional parameters to the logging option to indicate what
type of information to log.
l /Lx—Adds extra debugging information to the log (used in
previous example)
l /Lv—Specifies verbose output
Option Description
INSTALLDIR (Optional) Specify the absolute path for the directory in which you
want to install Toad. If you do not include this path, the installation
program defaults to:
C:\Program Files (x86)\Quest Software\Toad for SQL Server7.0.
ALLUSERS (Optional) Specify one of the following:
l For a per-machine installation, specify 1. This value allows
any user to use the Toad shortcut on the desktop after the
installation completes.
l For a per-user installation, enter the empty string value (“”)
This value allows only the user specified for USERNAME
(and the user that installed Toad) to see the Toad shortcut on
the target desktop. If USERNAME is omitted, only the user that
installed Toad sees the shortcut.
Note: If you do not specify this property, the installation program
defaults to a per-user installation.
USERNAME (Optional) Specify the user that intends to use Toad on the target
computer.
Notes:
Note: The Diagnostic Server is no longer used by Toad for SQL Server. If the Diagnostic Server was installed
with a previous release of Toad for SQL Server then uninstall that program. Use Control Panel | Programs and
Features | Uninstall or change a program and select to uninstall the Toad for SQL Server Diagnostic Server.
Caution: If you upgrade an automation script, it will no longer be compatible with earlier
versions of Toad.
3. Select No (and do not elect to save the script), to keep the script compatible with the previous version.
4. If you selected Yes, Toad upgrades your script and saves a backup copy of the original script in the
following location:
<application data directory>\Automation\bak\
5. If the script you upgraded is also scheduled, you must migrate the scheduling task, otherwise the
upgraded script will fail to run.
Caution! Migrating settings from a previous version of Toad may overwrite new settings files, implemented
for the current release (for example, updated reports templates, layouts, etc).
File Description
Action.log Tracks your usage within Toad. If you agree to share this data, the file is
automatically sent to Quest Software on a periodic basis.
Connections.xml Contains all connections stored in the Connection Manager or the New
Connection window.
ConnectionTrace.log Contains the SQL Output connection trace log file if you select Tools |
Execution Trace from the menu.
ExceptionTrace.log Contains a log of all exceptions encountered while running Toad.
FTPConnection.log Contains a log of exceptions encountered when attempting to connect to
FTP servers.
FTPConnections.xml Contains connections to FTP servers stored in the FTP Connections window.
Quest.PersistentCache.xml Contains the private object annotation cache options (object notes, Lookup
tables, and hidden columns). You can share these options with other Toad
users in Tools | Options | Database | Cache.
Settings.xml Contains many of the global configuration settings.
SqlServerPlanPrefs.xml Used to generate SQL Server execution plans.
ToadSupportBundle.zip Contains the last support bundle you generated.
l TYPE—Tabs that display on the right when you select an object in the
Object Explorer or Database Explorer.
Document Recovery Contains backup copies of Editor, Query Builder, and Database Diagram files
saved if you have enabled Document Recovery in Tools | Options
| Environment | General.
Keyboard Contains custom keyboard shortcut layouts.
Layouts Contains layouts for some areas in Toad, such as tool windows that
automatically display in the Editor and column layouts for the Messages tab.
ModuleSettings Contains general settings for various components in Toad, such as whether
the data grid defaults to read-only, displays not null indicators, etc.
Plugins Used by Toad plugin components.
Session Contains desktop configurations, including toolbar customizations and tool
window locations.
SQLFormatter Contains pre-set and user created templates for formatting SQL, and the
SQL statement used to preview formatting changes in the Formatting Options
page.
SQLRecall Contains the SQL statements saved by SQL Recall.
Templates Contains the following templates:
l Code Templates—Templates used to define default values when
creating new objects in the Object Explorer or Database Browser.
l Scripts—Startup scripts to run when connecting (InitialSqlServer.Sql).
l Snippets—Code Snippet entries.
l Reports—Report entries.
l Schema Compare
l Importing and Exporting Data
l Session Browser
l Performance Monitor
l Index Fragmentation
l and etc.
Note: 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. See "Troubleshoot SQL Server® Issues" on page 21 for more information about how to manually
restore Toad Plug-in.
Where:
[Type of Product/Mode] can be Uninstall, Freeware, Beta, Commercial, Trial
[TSS Installation Directory] is the directory where Toad for SQL Server resides.
Example:
C:\Program Files (x86)\Quest Software\Toad for SQL Server 7.0\SSMS
Installation\SsmsInstallation.exe Commercial "C:\Program Files (x86)\Quest
Software\Toad for SQL Server 7.0"
Uninstall Toad
If you uninstall Toad, it may not uninstall completely. When you use Toad, you create new files such as SQL
scripts, data output, or temp files, etc. The following types of files are not removed when you uninstall:
To uninstall Toad
1. Open the Windows Control Panel and select Programs and Features.
2. Select the product that you want to uninstall.
3. Click Uninstall.
l TCP/IP
l Named Pipes
Note: When establishing Named Pipes connection "Poll service status
in connection list" option should be cleared.
Parameter You can add parameters to the connection. Toad includes the Application
Name/Value Name parameter with value Toad for SQL Server by default.
4. Click Connect to save the connection and immediately connect to the database.
or
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.
1. Click .
Installation Issues
The following table describes issues related to installing Toad.
Issue Cause/Solution
When installing Toad on Solution:
Windows 7 64-bit, Program Select This program installed correctly to continue installation. For more
Compatibility Assistant may information, see http://windows.microsoft.com/en-PH/windows7/Program-
appear with “This program Compatibility-Assistant-frequently-asked-questions
might not have installed
correctly” message.
Connection Issues
Review the following solutions to help troubleshoot SQL Server connection issues in Toad.
Issue Cause/Solution
Cannot specify a port number Currently, Toad does not have a separate field for specifying a port number.
when connecting 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 Remote connections may not be enabled in SQL Server 2005. Also, named
instance in SQL Server 2005 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" You attempted to migrate settings from a previous install of Toad to the
error message when current install, but the settings file (InitialSqlServer.Sql) for the previous
connecting install was either removed, moved, or corrupt.
or You may also receive this error if you installed Toad and migrated settings
"Could not find a part of the from a previous version, and later uninstalled the previous version.
path Solution:
C:\Program Files\Quest You must specify a valid location for the InitialSqlServer.Sql file in Toad.
Software
\Toad for SQL
To specify a valid location
Server\Template\Scripts\
InitialSqlServer.Sql" error 1. Open the SQL Server options page under Tools | Options |
message when connecting 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 If you are trying to connect to the server using Named Pipes, "Poll service
Prerequisites
You must install a supported version control client on the computer where Toad is installed. The following table
lists the supported version control providers and the versions tested with Toad.
Supported
Provider Server Version Tested Client Version Tested
Apache Subversion 1.7.5 on CollabNet Subversion Command-Line Client 1.7.5
Subversion™ Windows Note: Any Subversion client must have svn.exe in its installation
directory to use version control in Toad.
Git Toad works only with the local repository. For commands such as clone, pull and push use
an external tool.
Team TFS 2008, 2010, 2012, Visual Studio® (2008, 2010, 2012, 2013) Team Explorer Client
Foundation 2013, 2015
Server (TFS)
File system Toad allows to utilize practically any version control system using the external client tool. In
based this case Toad Version Control tool works with the directories at local HDD while you commit
changes to the repository with version control client tool.
TABLE
VIEW
STORED PROCEDURE
FUNCTION
SEQUENCE
UDDT
RULE
DEFAULT
SQL SCRIPT
Note: Additional functionality and compatibility with older clients is possible but out of scope of what we are
able to test.
Note: Even if you previously configured version control for objects, you must run the Version Control
Wizard again to configure version control for files.
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.
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.
Additional Actions
l 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.
4. Manage object and scripts using Version Control. See "Manage Objects under Version Control" on page
29 for more information.
Use To...
Show perspective Select to review all controlled objects for current configuration.
Diff Select to review differences between the object script in your local
database and the object's revision that was applied to it.
Note: Diff is unavailable for File System Based configuration.
Diff with latest revision Select to review differences between the object script in your local
database and the latest revision in the version control repository.
Example: You got the latest object revision from the repository 2 days ago. By the time you did it, the
latest revision was 5. Yesterday your colleague worked with the same object and committed changes
in the repository, which are now marked as revision 6.
Today you altered the object's script and want to see the differences. You can select one of the
following:
l Diff—To compare the object in your local database with revision 5.
l Diff with latest revision—To compare the object in your local database with revision 6.
Show history Select to review all commits for selected object.
Tip: Select Show history on database to review all commits.
Note: Show History is unavailable for File System Based
configuration.
Get latest revision Select to apply object's changes from the version control repository to
your local database. The synchronization script is generated to update
selected object to the latest revision.
Commit Select to apply object's changes from your local database to the
version control repository.
Note: You should write a comment when committing changes.
Undo changes Select to rollback changes in your local database. The synchronization
script is generated to revert object to the revision which was a applied
last time.
Update status Select to compare a script in your local database with the script in the
repository. New status will be issued according to the comparison
results.
Add to ignore list Select to exclude object from the version control. Ignored objects are
not listed in Controlled Objects pane, Commit and Get latest revision
are disabled.
Remove from ignore list Select to set object status as Untracked and add it to version control.
Open in Windows Explorer Select to navigate to the file in the Windows Explorer.
l In previous releases, the method Toad used to generate the script was different than the current method.
After upgrading Toad and reconfiguring version control, the local revision of the objects differs from
version control repository (The objects have Unknown status). If the object in your database is current,
you should commit it into version control.
Apache Description
Subversion™
Issues
System If a message stating that, “The system cannot find the file specified” displays, this usually
cannot find means that the Subversion executable cannot be found in the path you specified in the
file BinaryPath field of the Command Based Version Control Properties window. Verify that
svn.exe exists in the directory you specified in this field.
Command When executing Subversion commands, user input is not allowed. This presents an issue
execution 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.
OutOfMemory When adding a large number of objects, Subversion may encounter OutOfMemory
exception exception.
when adding Workaround:
a large
Commit objects in several steps.
number of
objects
SVN is If Subversion is missing in the list of available version control providers, it means that
missing in the Subversion.xml was removed or corrupted.
list of Workaround:
available
Contact Support to get a new Subversion.xml and place it under <Toad install
providers
path>/Templates/Version Control/.
Object Issues Description
Adding When you add multiple objects to version control, the objects are grouped and added in
multiple batches (for example, all the tables for a particular schema are added at once). If an error
objects failed (for example, failure to support Korean characters) causes this command to fail, none of
the objects are added.
SQL Server 2012 and SQL Server 2014 Platforms Tested for Debugging
Client Server
2003 EE
(SP1)
Vista
Server
2008
Client Server
2003 EE
(SP1)
Vista
Server
2008
Client Server
2003 EE
(SP1)
Vista
Server
2008
Client Server
2003 EE
(SP1)
Vista
Server
2008
2. If autocommit is disabled, commit or rollback the connection in Toad before starting the
debugging session.
Note: If you are unable to locate this file, you can run the remote debugging setup component
(rdbgsetup.exe). This file is located by default in the following directory on the server where SQL
Server 2005 is installed:
C:\Program Files\Microsoft SQL Server\90\Shared\1033
2. Make sure the following permissions are set:
l Your Windows account that Toad is running under must be a member of sysadmin server role in
the SQL Server being debugged.
l Your server login must also be a member of the sysadmin role. This login can be your Windows
user account (Windows authentication), or a SQL Server login (SQL Server authentication).
To create a server login from your Windows account and add it to the sysadmin role, a user who
already has sysadmin privileges must execute the following:
sp_addsrvrolemember 'Domain\Name', 'sysadmin'
Note: The Remote Procedure Call (RPC) service should be started on both the Toad
client and server.
2. Make sure the following permissions are set:
l Your Windows account that Toad is running under must be a member of the sysadmin server role
for the instance you are debugging.
l Your server login must also be a member of the sysadmin role. This login can be your Windows
Set Up Debugging
The Debugger Setup wizard checks your database library and settings files on both the server and client system
to identify conflicts with the Debugger.
The wizard verifies the following on the server:
l Existence of the corresponding DLL files
l DLL version (determines whether Toad has permission for their verification)
l COM registration
l DCOM support
Contact Quest
For sales or other inquiries, visit www.quest.com/contact.
A M
application virtualization 6 manage objects under Version Control 29
automation
R
migrate scheduled tasks 13
requirements
upgrade scripts 12
Citrix 6
C client 5
Citrix virtualization 6
install 11
S
requirements 6
server virtualization 6
client requirements 5
silent install 9
connections
SQL Azure
create SQL Azure 19
create connections 19
create SQL Server 19
SQL Server
share for all session windows 18
configure debugging 34
troubleshoot SQL Server 21
create connections 19
understand 18
troubleshoot 21
corporate deployment 9
Subversion, configure 28
D system requirements 5
debugger
T
configure SQL Server 34
Team Foundation Server, configure 28
verify installed components 39
TFS, configure 28
desktop virtualization 6
Toad Plug-in 15
I troubleshoot
install 8 SQL Server connections 21
Citrix 11 version control 32
Citrix support 6
U
client requirements 5
uninstall 16
silent 9
intergration with Management Studio 15