ToadDataStudio 1.0 InstallationGuide
ToadDataStudio 1.0 InstallationGuide
Installation Guide
Copyright
Copyright 2
Contents 3
Installation 6
System Requirements 6
Client Requirements 6
Server Requirements 8
Virtualization Support 10
User Requirements 10
Install Toad 12
Troubleshoot Installation Errors 13
Specify Application Data Directory Location 13
Install Toad Silently 14
Determine Which Installer to Use 14
Silent Installation Prerequisites 15
Silent Installation Using the Executable 15
Silent Installation Using the Microsoft Installer 17
Install Toad on Citrix® Systems 18
Uninstall Toad 19
Configure Toad Layout 19
Customize Your Toad Workspace 22
Create Connections 23
Understand Toad Connections 23
Toad Open Connections 23
Sharing a Connection Among Windows 24
Create Access Connections 24
Considerations and Limitations 25
Create Amazon Redshift Connections 25
Create SAP Business Objects Connections 26
Configure DB2 Client Connections 28
Configure DB2 Client Connections 28
Maintain DB2 Client Connections 31
Configure DB2 LDAP Support 33
Create Toad Connection Profiles for DB2 33
Connection Using a Custom Connection String 34
Create Connection Profiles 34
Manage Connections 35
Create Excel Connections 36
Considerations and Limitations 38
Troubleshoot Connections 66
Troubleshoot Access Issues 66
Missing Functionality and Object Information 66
Other Issues 66
How to Connect to Apache Hive Using Kerberos Authentication 66
Troubleshoot Excel® Issues 69
Excel Connections 69
Working with Excel Files 71
Opening Excel Files in Toad Document Window 71
Troubleshoot DB2 LUW Issues 71
Installation Issues 71
About Us 81
Contact Quest 81
Technical Support Resources 81
Index 82
System Requirements
Review the following client and database server requirements for Toad® Data Studio.
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 8 GB of RAM minimum, 16 GB recommended
Additional RAM Requirements: Using Local Storage, Cross-Connection Query, Business
Intelligence connections, or NoSQL connections can require an additional 500 MB of RAM.
These features start processes (mysqld.exe, hubproxy.exe) which persist for the Toad
session.
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 450 MB to run Toad
Additional Recommendations: For retrieving large queries, allow 10 GB free disk space (or
more, depending on the size of the data being retrieved). After retrieving 2500 rows, Toad
saves data in a TMP (.tmp) file in the user's Temp directory. These TMP files are deleted
when Toad closes.
Operating Windows Server® 2012
System Windows Server® 2012 R2
Windows Server® 2016
Windows Server® 2019
Windows® 8.1
Windows® 10
To create a connection to an Amazon Redshift database you must install the Amazon
Redshift ODBC driver 1.3.1.1000 (or later version) on client computers accessing an Amazon
Redshift data warehouse. For each computer where you install the driver, there are the
following minimum requirements that you can find on the Amazon Redshift Web site.
For more information regarding the process of creating Amazon Redshift connections, please
refer to the Installation Guide and User Guide.
Additional Web Browser
Requirements Microsoft® Internet Explorer® 11 or later
Screen
Recommended maximum DPI settings for Toad are 125%. It is possible to use Toad up to
200% but some dialog windows will not be completely usable anymore.
Maximum tested resolution for Toad is 3800 x 2160 px.
Requirement Details
Native Database Toad supports the following databases:
Server Oracle 10g R2, 11g, 11g R2, 12c, 12c R2, 18c,19c, 21c
Toad has been tested on Oracle Exadata 2.0 running Oracle database 11g R2.
SQL Server 2012 and SQL Server 2012 Express
SQL Server 2014 Enterprise and SQL Server 2014 Express
SQL Server 2016
SQL Server 2017
SQL Server 2019
Notes:
l SQL Server Compact Edition is not supported.
l Storage Management is not available on SQL Server Express.
IBM DB2 for LUW 9.7, 10.1, 10.5, 10.5.0.5, 11.1, 11.5
IBM DB2 for z/OS 11, 12
Note: Toad may support IBM DB2 Express and SWE in addition to listed above servers
but note that no testing was performed on it.
Note: Windows 8, 10 and Windows Server 2012 require the following Fix Pack in order to
ensure registration of DLLs in Global Assembly Cache:
IBM DB2 LUW 10.5 Fix Pack 4
IBM DB2 LUW 10.1 Fix Pack 4
IBM DB2 LUW 9.7 Fix Pack 10
MySQL 5.0, 5.1, 5.5, 5.6, 5.7
MariaDB 5.5.5, 10.2.8, 10.3.2 (using MySQL provider)
SAP ASE 15.5, 15.7, 16 SP03
SAP IQ 15, 16
SAP SQL Anywhere 16
SAP HANA SPS 08, SPS 09, SPS 10, SPS 11, SPS 12, SAP HANA 2.0, SAP HANA 2.0
SPS 02
Teradata 12.0, 13.0, 13.10, 14, 15, 16
Access® 2007, 2010, 2013, 2016
Note: To use Access 2016 64-bit to connect to an Access database in Toad, the Microsoft
Access Database Engine is required and might not be included in the Access installation.
The engine must match the architecture (bitness) of Toad.
Excel® 2003, 2007, 2010, 2013, 2016
Note: To use Excel 2016 64-bit to connect to an Excel or .csv file in Toad, the Microsoft
Access Database Engine is required and might not be included in the Excel installation.
The engine must match the architecture (bitness) of Toad.
ODBC Database Toad Data Studio allows you to create a connection to a database that supports an ODBC
Server 3.0 or later driver. ODBC connectivity provides basic querying capability, but may not be
as full-featured as a native connection in Toad. Toad has been tested on the following
databases, using an ODBC connection:
l DB2 for i5/OS V5R4 and IBM i 6.1, 7.3
l EDB Postgres Advanced Server 10
Virtualization Support
Requirement Details
Application When deploying Toad in a virtualization environment, for best results ensure the system
Virtualization 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 18 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
User Requirements
2. Select a destination folder and other options. Review the following for additional information.
Install Wizard
Page Description
Destination Select a destination folder or use the default.
Folder
Additional Allow saving passwords—(default) Select to allow Toad to save passwords for
Properties data source connections.
Prohibit saving passwords—Select to prohibit Toad from saving connection
passwords.
Note: If this option is selected, the Automation module will be disabled in this
installation of Toad.
See the following table for default (Roaming) and resulting (Local) directory path.
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.
Command-Line Options
The following MSIEXEC command-line options are used in this example:
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
l /L*—Log all information, except that specified by x and v
l /L*v—Log all information, including v (verbose output)
l /L*x—Log all information, including x (extra debugging info)
l /L*vx—Log all information, including that specified by v and x
See the log section at http://msdn2.microsoft.com/en-
us/library/aa367988.aspx for more information about additional logging
parameters.
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 \Quest Software\Toad Data Studio1.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:
l If ALLUSERS is omitted or defined with the empty string value
(""), only the user specified here (and the user that installed
Toad) can see the Toad shortcut on the desktop after the
installation completes.
l If ALLUSERS is omitted or defined with the empty string value
("") and you omit the USERNAME option, only the user that
installed Toad sees the Toad shortcut on the desktop.
l If ALLUSERS is 1, the USERNAME value is ignored during
installation.
COMPANYNAME (Optional) Specify the name of the company that owns this
installation.
ALLOWPASSWORDS=FALSE (Optional) Set in order to prohibit users from saving their passwords
in Toad.
OPTIONSTEMPLATE (Optional) Enter a full path to the Options Template that you
generated in Tools | Options | General.
MSI Prerequisites
Visual C++ Redistributable for Visual Studio 2015 is required by Toad, however it is not installed when you use
the Microsoft (.msi) installer. Ensure that this software is installed prior to performing an install using the .msi
installer. For downloads, see Visual C++ Redistributable for VS 2015. For related information, see KB2999226 -
Update for Universal C Runtime in Windows.
Install both vc_redist.x86.exe and vc_redist.x64.exe.
This software is required to enable some features in Toad Data Studio, such as Local Storage. This software is
included in installation when using the executable (.exe) installer.
2. For a standard installation with all features enabled, enter the following command:
msiexec /i “ToadInstaller.msi” /q
You can customize command-line options and overrides for your installation similar to the following:
msiexec /i “ToadInstaller.msi” INSTALLDIR= “Drive:\your_install_path” /q
USERNAME=”someone” COMPANYNAME=”your_company” ALLUSERS=1
Command-Line Options
The following MSIEXEC command-line options are used in this example:
Option Description
/i Run the installation.
/q Specify the user interface (UI) that displays during installation. You can append
other options, such as n to hide the UI or b to hide the Cancel button during the
installation.
Note: All command-line options are case-insensitive. See http://msdn2.microsoft.com/en-
us/library/aa367988.aspx for a complete list of command-line options.
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 \Quest Software\Toad Data Studio1.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:
l If ALLUSERS is omitted or defined with the empty string value
(""), only the user specified here (and the user that installed
Toad) can see the Toad shortcut on the desktop after the
installation completes.
l If ALLUSERS is omitted or defined with the empty string value
("") and you omit the USERNAME option, only the user that
installed Toad sees the Toad shortcut on the desktop.
l If ALLUSERS is 1, the USERNAME value is ignored during
installation.
COMPANYNAME (Optional) Specify the name of the company that owns this
installation.
ALLOWPASSWORDS=FALSE (Optional) Set in order to prohibit users from saving their passwords
in Toad.
OPTIONSTEMPLATE (Optional) Enter a full path to the Options Template that you
generated in Tools | Options | General.
Notes:
l All default installation option overrides are case-sensitive.
l Enclose all values (except for the ALLUSERS value) in double quotations.
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:
l Any new files you create
l Any copies of files you make for backup purposes
l Settings files
You can uninstall Toad Data Studio by using the Installer or by using the Windows Add/Remove Programs (or
Uninstall a program) feature. Using the Installer is the preferred way to uninstall Toad Data Studio.
To uninstall Toad
1. Run the ToadInstaller.exe.
2. Select Uninstall Toad Data Studio only.
3. To customize your layout, select Custom and click Next. Then specify options on each page of the wizard.
Review the following for additional information:
Page Options
Look and Feel Select a skin and grid style.
l Skin—Applies the skin style you select to document
windows, tool windows, and modal dialogs.
l Grid style—Applies the grid style you select to the data grid
only.
A preview of the selected style is automatically displayed in the
wizard and in the grid.
Tip: You can change the skin and grid style later in Tools |
4. Click Connect to connect immediately while saving the connection information. Optionally, click Save to
save the connection without connecting.
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory
link in Help | About.
Click here to view a video about creating connections in Toad Data Studio
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.
URL Enter the Business Objects URL to which you want to connect. This is the URL to
the Query as a Web Service component of the Business Objects installation. See
"Important Information about Business Objects Connections" on page 27 for more
information.
Note: The URL should be in the following format:
http://<server>:<port>/dswsbobje/qaawsservices
Password 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.
Category (Optional) Select an existing category or create a new one.
Note: In NoSQL and Business Intelligence connections, Toad automatically saves the password in the
connections.xml file as obfuscated text, as well as in Toad. To add additional password security, use
Toad's Master Password feature.
4. Click Connect to connect immediately while saving the connection information. Optionally, click Save to
save the connection without connecting.
5. Upon creating an initial connection, Toad automatically maps the data source objects. This process
runs in the background, and until it is finished, you may experience a delay when attempting to access
these objects.
Where <server> corresponds to your web server address, and <port> corresponds to the port where you set
up in your web server. (dswsbobje is the default name of the Query as a Web Service web application.)
An example URL is http://server01:8080/dswsbobje/qaawsservices.
Tips:
l
To specify a default value for a column parameter, select a Query and click .
l Connections are stored in the connections.xml file and can be found by clicking the Application Data
Directory link in Help | About.
l You can specify a proxy server to use for Business Intelligence and NoSQL connections at Tools | Options
| Database | Data Services.
Note: If the Client Configuration Wizard opens, Toad found only one DB2 client installed.
2. From the DB2 Client list, select the name of the DB2 client whose catalog you want to transfer to your
default DB2 client.
This list contains all current previously installed DB2 clients on your computer, including the default DB2
client instance and any Toad DB2 client installations.
3. Click OK.
4. To create a connection in Toad for any of the transferred catalog entries, see Create Toad Connection
Profiles for DB2.
Import a DB2 catalog previously exported to a file
1. In the Connections (or Create New Connection) window, click beside the Database alias drop-down list
to open the Client Configuration wizard.
2. On the Welcome page, select Import Profile.
3. Click Next.
4. Click in the Profile name field to browse for and select the exported profile you want to import. When you
select the profile, its contents display in the text pane.
1. In the Connections (or Create New Connection) window, click beside the Database alias drop-down list
to open the Client Configuration wizard. The Welcome page displays, showing the DB2 client's existing
catalog configuration in a tree view.
2. If the host and node names for the database you want to configure are listed in the tree, select them. These
selections pre-fill certain fields required later in the wizard process. If these names are not listed, you must
provide the necessary host and node information later in the wizard.
3. Click Add Catalog Entry.
4. Review the following for additional information:
1. In the Connections (or Create New Connection) window, click beside the Database alias drop-down list
to open the Client Configuration wizard. The Welcome page displays, showing the DB2 client's existing
catalog configuration in a tree view.
2. If the host name for the DB2 subsystem you want to configure is listed in the tree, select it. This selection
pre-fills certain fields required later in the wizard process. If the host name is not listed, you must provide the
necessary host information later in the wizard.
3. Click Add Catalog Entry.
4. Review the following for additional information:
5. Complete the wizard. A message informs you whether the entry was added successfully.
The Database alias drop-down list in the Connections window shows the alias for the newly cataloged
subsystem. To complete the Toad connection setup, create a Toad connection profile for the database. See
"Create Toad Connection Profiles for DB2" on page 33 for more information.
Manually catalog DB2 Connect gateways
In order to connect to a DB2 for z/OS subsystem, you need to catalog two entries. First, you need to catalog the DB2
subsystem on the DB2 Connect gateway. During this process, you define an alias for the DB2 subsystem. Second,
you need to catalog this DB2 subsystem alias in Toad. The procedure below describes both cataloging events.
1. In the Connections (or Create New Connection) window, click beside the Database alias drop-down list
to open the Client Configuration wizard.
1. In the Connections (or Create New Connection) window, click beside the Database alias drop-down list
to open the Client Configuration wizard.
2. In the catalog configuration tree for the DB2 client, expand one or more nodes, and select the catalog entries
that you want to remove. (Press CTRL+click to select multiple entries.)
Note: You can remove a node by selecting all database entries for that node.
3. Click Remove Catalog Entry.
4. On the Catalog Script Review page, modify the script in the preview pane as needed.
5. Click Finish. A message window displays, informing you whether the removals completed successfully.
Export the catalog for the current DB2 client
Toad provides functionality to export your current DB2 client catalog to a file, called an export profile. You can then
import this profile to set up the catalog for another DB2 client.
To create the export profile containing the current DB2 client catalog, Toad executes the DB2 Connectivity
Configuration Export Tool command db2cfexp. If you want to export the catalog of a remote or local DB2 client
(other than your current DB2 client), you must manually execute this command.
1. In the Connections (or Create New Connection) window, click beside the Database alias
drop-down list.
2. Click Export Profile in the Welcome window of the Client Configuration wizard. (You might need to click
this button.)
3. Click Next.
4. Click in the Profile name field to browse for and select the path for the profile in which to export the
current DB2 client catalog.
5. Select the type of profile you want to create:
l Template to create a profile used as a template for other DB2 clients (default for exporting a
DB2 catalog)
l Backup to create a profile used to back up a DB2 database instance
The port number defaults to 389 (default LDAP port) if you leave the port number blank.
4. Exit the Command window.
5. Launch Toad and open the Connections window.
Databases on the LDAP server should be available from the Database alias drop-down list in the
Connections window. To complete the Toad connection setup, you must create a Toad connection profile for
each database. See "Create Toad Connection Profiles for DB2" on page 33 for more information.
Note: When you connect using IBM Data Server Driver the Database button and the toolbar option in Tools | LUW
Database Options will not be available.
Click here to view a video about creating connections in Toad Data Studio
(See "Export connection profiles to an XML file" on page 35 for more information about exporting a profile
that you can later import.)
Note: The connection profiles are not usable unless you have also created entries in the DB2 catalog for the
DB2 databases and subsystems to which these profiles correspond. See "Configure DB2 Client
Connections" on page 28 for more information.
1. In the Connections (or Create New Connection) window, click on the toolbar, and select
Connection file.
2. From the Import Connections window, browse for and select the XML file containing the connection
profiles you want to import.
3. Click Open.
4. Select DB2 and click OK to complete the import.
The connections whose profiles you imported are listed on the Connections window.
l Manually define Toad connection profiles.
1. In the Connections (or Create New Connection) window, click on the toolbar (ALT+F+N).
2. Select IBM DB2 LUW or IBM DB2 z/OS from the Group list box.
3. Review the following for additional information:
Database alias Select the alias for the DB2 database or subsystem. This alias was defined
when you cataloged this DB2 database or subsystem on the DB2 client. See
"Configure DB2 Client Connections" on page 28 for more information if the
alias does not display in the list.
Tip: Click to refresh the alias list. Normally, Toad caches the DB2 catalog
the first time you open this window in your Toad session and continues to read
from cache each time you subsequently open this window. This button forces
Toad to reread the DB2 catalog to list any new systems that might have been
cataloged externally during the caching period.
Default Enter the SET SCHEMA value (DB2 for LUW) or the SET SCHEMA or SET
schema/auth ID CURRENT SQLID value (DB2 for z/OS) for this connection.
Category 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.
4. Select the Advanced tab to define special register values that are then in effect each time Toad
connects to the DB2 database or subsystem.
5. Click Connect to save the connection and immediately connect to the database.
or
Click Save to save the connection without connecting to the database.
Manage Connections
After you have completed both phases for configuring Toad connections to DB2 databases or subsystems, the
Connections window lists all the configured connections, allowing you to perform the following:
l Connect to and manage a DB2 database or subsystem through Toad
l Export connection profiles to an XML file
Toad for DB2 provides functionality to export one or more of your current Toad connection profiles to an
XML file. You can then import these exported connection profiles into another Toad installation. See "Import
Toad connection profiles previously exported to an XML file " on page 34 for more information.
3. On the Export Connections window, review the selected connections, and click OK.
4. Browse for and select the path for the file in which to export the selected profiles.
l
In the Connections or Connections Manager window, click .
l Troubleshoot connection issues
Note: Click to open the Client Configuration Wizard. See "Configure DB2 Client Connections" on page 28 for
more information.
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory
link in Help | About.
4. Click Connect to connect immediately while saving the connection information. Optionally, click Save to
save the connection without connecting.
l
Select on the Connections toolbar to open the Connections dialog. Select the Excel file connection in the
left pane to view the connection properties in the right pane.
Troubleshoot Excel
To troubleshoot Excel issues, see the following:
l See "Troubleshoot Excel® Issues" on page 69 for more information about troubleshooting Excel
connection issues.
l For a list of Excel file limitations from Microsoft, see Microsoft Excel specifications and limits.
Click here to view a video about creating connections in Toad Data Studio
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory
link in Help | About.
URL Enter the full URL address to the SharePoint OData service endpoint for the
SharePoint site to which you want to connect.
The URL address should have the following format:
http://<servername>/_vti_bin/listdata.svc
Authentication Select the type of authentication to use for this connection. Toad offers two options:
l Basic Authentication
l Active Directory Universal with MFA
The required login fields will be enabled or disabled according to the authentication
4. Click Connect to connect immediately while saving the connection information. Optionally, click Save to
save the connection without connecting.
5. Upon creating an initial connection, Toad automatically maps the data source objects. This process
runs in the background, and until it is finished, you may experience a delay when attempting to access
these objects.
Tips:
l Connections are stored in the connections.xml file and can be found by clicking the Application Data
Directory link in Help | About.
l You can specify a proxy server to use for Business Intelligence and NoSQL connections at Tools | Options
| Database | Data Services.
After completing the final authentication step, a successful connection to SharePoint will be made.
2. In the Group list, select Google Analytics. The Google log-in page immediately displays within the Create
New Connection dialog.
3. Enter the credentials (email address and password) for your Google account and click Sign in.
Note: If you have multiple Google accounts and have previously logged in to Google (or connected through
Toad), the Google log-in page may display the last Google account used. To specify a different Google
account for the new connection, use the Google links/menu to select another account.
4. (optional) You can enter a name for your new account and select a category. You can also make these
modifications later using the Connection Properties dialog.
5. In the Google authorization page that displays, click Accept to allow Toad access to your Google Analytics
data. Toad then attempts to establish a connection to Google Analytics. If the connection is successful, the
Create New Connection dialog closes.
6. Upon creating an initial connection, Toad automatically maps the data source objects. This process
runs in the background, and until it is finished, you may experience a delay when attempting to access
these objects.
Reauthorizing a Connection
If you encounter an error message when attempting to connect using your Google Analytics connection, Toad's
authorization (access) to the Google account for that connection may have been lost. Use the following procedure to
re-establish authorization for the connection.
You can also use this procedure to specify a different Google log-in account for a connection.
To Reauthorize
1. In the Navigation Manager, disconnect from the connection. You must disconnect before you can
re-authorize.
2. After disconnecting, right-click the connection and select Properties.
3. In the Connection Properties dialog, click Reauthorize.
l If you are no longer logged in to Google, the Google log-in page displays.
l To reauthorize using the same Google account, re-enter your Google account credentials
and click Sign-in. Then click Accept on the authorization page.
l To specify a different Google account for this connection, use the Google links to switch the
account just as you normally would in the Google Web site. Once you specify a different
account, this is the Google account associated with this connection in Toad. Click Sign-in.
Then click Accept on the authorization page.
l If you are still logged in to Google, the Google page for granting Toad access to your Google
Analytics data displays.
Server tab
Host Enter the host name or IP address of the Hive data source.
Port Enter the port number.
Schema Enter a Hive schema to open upon connection.
(HiveServer2 only) After connecting, you can select a different available schema in
the Object Explorer.
Server type Select the version of HiveServer the host uses, HiveServer1 or HiveServer2.
Use SSL (HiveServer2 only) Select to use SSL to connect to Hive.
HTTP mode (HiveServer2 only) Select to connect to HiveServer2 running in HTTP mode. Then
enter the service endpoint. The default is cliservice.
Session (HiveServer1 only) Enter any Hive session initialization commands.
Initialization These commands will be executed once, at the start of each connection.
Category (Optional) Select an existing category or create a new one.
Authentication
tab
(HiveServer1)
Connect with SSH Select to use SSH to connect to Hive. Then enter a user name and select an
authentication method (key file or password).
SSH user Enter the user name to log in when using SSH.
SSH port Select the SSH port number. The default is 22.
Authenticate with Select if the host uses a key file to authenticate the SSH user field.
a key file Private key path—Enter the absolute path (including file name) to the private key
file on the host (not the client).
Pass phrase—Enter your passphrase.
4. Click Connect to connect immediately while saving the connection information. Optionally, click Save to
save the connection without connecting.
5. Upon creating an initial connection, Toad automatically maps the data source objects. This process
runs in the background, and until it is finished, you may experience a delay when attempting to access
these objects.
Tips:
l Connections are stored in the connections.xml file and can be found by clicking the Application Data
Directory link in Help | About.
l You can specify a proxy server to use for Business Intelligence and NoSQL connections at Tools | Options
| Database | Data Services.
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.
4. To create a data source to use in this connection, click in the Data Source Name field. Then click Add.
Notes:
l If you have an Oracle database with Unicode data, make sure to select Force SQL_WCHAR Support
on the Workarounds tab of the windows Oracle ODBC Configuration dialog. If you do not, you will not
be able to see the data.
l If creating a MySQL ODBC connection to use in a cross-connection query, you must specify a
database in the Windows MySQL ODBC Configuration dialog.
7. Specify the connection properties in the Create New Connection dialog. Review the following for additional
information:
General
Data source Select the driver or data source name you added in the previous steps.
name
User Enter the user name to use when connecting.
Password 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.
8. Click Connect to connect immediately while saving the connection information. Optionally, click Save to
save the connection without connecting.
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory
link in Help | About.
ODBC Features
Feature Description
Bypass schema/instance For ODBC connections, in the SQL Editor you can bypass selecting a
selection in SQL Editor schema/instance and specify this information through the script instead. This is
useful if your script executes SQL against multiple schemas.
To use this method, select I will set schema/instance in the script from the
schema/instance drop-down list in the SQL Editor window. Then specify the
schema/instance through your script.
Click here to view a video about creating connections in Toad Data Studio
Notes:
l To connect using LDAP, you must install an Oracle client on the computer.
l Toad supports a 9i, 10g, and 11 client and the Oracle Instant client. If you want to use the instant client, you
must configure it to work with Toad. See "Configure the Oracle Instant Client" on page 48 for more
information.
5. To use the Oracle Instant Client connection in a cross-connection query, you must also install an
Oracle ODBC driver. (While the Oracle Client full install includes an ODBC driver, the Oracle Instant
Client does not.)
4. Click Connect to connect immediately while saving the connection information. Optionally, click Save to
save the connection without connecting.
Note: Go to Tools | Options | Database | Oracle to specify default options to use in Oracle connections.
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory
link in Help | About.
URL Enter the URL to the Oracle Business Intelligence Enterprise data source to which
you want to connect.
Note: You must include the port number in the URL as in the following examples:
format—http://<server path>:<port>/analytics/saw.dll
example—http://server01.mycompany.com:80/analytics/saw.dll
Password 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.
Row Limit Select a row limit to enforce for query results.
default = 500,000
Category (Optional) Select an existing category or create a new one.
Note: In NoSQL and Business Intelligence connections, Toad automatically saves the password in the
connections.xml file as obfuscated text, as well as in Toad. To add additional password security, use
Toad's Master Password feature.
4. Click Connect to connect immediately while saving the connection information. Optionally, click Save to
save the connection without connecting.
4. To create a data source to use in this connection, click in the Data Source Name field. Then click Add.
a. Select a PostgreSQL ODBC driver from the list, and click Finish.
b. Specify the configuration properties required for the database in the Windows driver setup dialog.
Save your settings when finished.
5. Specify the remaining connection properties in the Create New Connection dialog. Review the following for
additional information:
Note: Specify a user that has been granted SELECT privilege in pg_catalog schema.
General
Data source Select the driver or data source name you added in the previous steps.
6. Click Connect to connect immediately while saving the connection information. Optionally, click Save to
save the connection without connecting.
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory
link in Help | About.
ODBC Features
Feature Description
Bypass schema/instance For ODBC connections, in the SQL Editor you can bypass selecting a
selection in SQL Editor schema/instance and specify this information through the script instead. This is
useful if your script executes SQL against multiple schemas.
To use this method, select I will set schema/instance in the script from the
schema/instance drop-down list in the SQL Editor window. Then specify the
schema/instance through your script.
Note: When this option is selected, some code completion features, object
actions, and object information tool tips are unavailable for this SQL Editor
window.
Click here to view a video about creating connections in Toad Data Studio
2. Select Salesforce from the Group list. The Create New Connection dialog opens.
b. After entering the connection information, click Connect to connect immediately while saving the
connection information. Optionally, click Save to save the connection without connecting.
4. To create a Salesforce connection using your corporate credentials (single sign-on), select the Corporate
Credentials tab.
a. Enter your company's custom Salesforce URL. An example is https://company.my.salesforce.com
or http://salesforce.servername.
Note: If you authenticate and request login to Salesforce through your company's server (e.g.,
http://salesforce.servername), you may need to contact your IT department to obtain the full URL to
enter in this step.
b. If the Salesforce log-in page displays, enter your corporate credentials (user name and password)
and click Log in to Salesforce.
Note: The Salesforce log-in page does not display when authenticating through your
company's server.
c. The Salesforce consent page displays. Click Allow to allow Toad access to your Salesforce data.
5. Upon creating an initial connection, Toad automatically maps the data source objects. This process
runs in the background, and until it is finished, you may experience a delay when attempting to access
these objects.
Note: In NoSQL and Business Intelligence connections, Toad automatically saves the password in the
connections.xml file as obfuscated text, as well as in Toad. To add additional password security, use Toad's Master
Password feature.
To Reauthorize
1. In the Navigation Manager, disconnect from the connection. You must disconnect before you can
re-authorize.
2. After disconnecting, right-click the connection and select Properties.
3. In the Connection Properties dialog, click Reauthorize in the Corporate Credentials tab.
4. If the Salesforce log-in page displays, re-enter your corporate credentials.
Note: The Salesforce log-in page does not display when authenticating through your company's server.
Tips:
l Connections are stored in the connections.xml file and can be found by clicking the Application Data
Directory link in Help | About.
l You can specify a proxy server to use for Business Intelligence and NoSQL connections at Tools | Options
| Database | Data Services.
Authentication There are four types of authentication that you can use to connect to Snowflake in
Toad. The required Login fields will change according to the type of authentication
you select. All the authenticators are located in a dropdown list:
l Snowflake – User account authentication
l SSO – Single Sign-On via external browser
l OAuth – Token-based authentication
l MFA - Multi-Factor Authentication
l Key pair - JSON Web Token (JWT)
User Enter the username for your Snowflake account
Password Enter the password for your Snowflake account
Token Enter your authentication token (Only visible when connecting via OAuth)
Private key path Enter your Private key (Only visible when connecting via Key pair)
Passphrase Passphrase is required only if the keys are encrypted (Only visible when
connecting via Key pair)
Port The default port number for Snowflake is 443
Optional A connection can be made without providing this information
Role Enter the user role that you would like to connect to
Warehouse Enter the name of the Warehouse you would like to connect to
Database Enter the name of the Database(s) you would like to connect to
Schema Enter the name of the Schema(s) you would like to connect to
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.
Authentication Notes
When using SSO or MFA, there is a way to maintain continuous and secure connectivity without needing to enter
login credentials for each connection attempt to Snowflake (as well as to prevent additional browser loading
whenever a new module is started in Toad Data Studio). To achieve this, check whether the correct parameters
have been set in your account by executing the query below in your Snowflake cloud interface:
The output that will secure login credentials caching will have these values:
For SSO
allow_id_token = true;
For MFA
allow_client_mfa_caching = true;
If these values are set to false, then the following queries need to be executed:
For SSO:
ALTER ACCOUNT
SET allow_id_token = true;
For MFA:
ALTER ACCOUNT
SET allow_client_mfa_caching = true;
Note: If a Role or Warehouse isn’t chosen, the default settings from the Snowflake User account will be applied (it is
considered best practice that a user sets a default Role and a default Warehouse in their Snowflake user account).
Tip: It is strongly advised to use only the Snowflake user account authentication when creating Automation scripts
to avoid unnecessary workflow interruptions.
2. Select Microsoft SQL Server or Microsoft SQL Azure from the Group list box.
3. Review the following for additional information:
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 .
After completing the final authentication step, a successful connection to Microsoft SQL Azure will be made.
2. Select Microsoft SQL Server Analysis Services (SSAS) from the Group list.
3. Enter the connection information in the Create New Connection dialog. Review the following for additional
information:
URI Enter the URL for the Analysis Services data source to which you want to connect.
Note: Toad connects to Analysis Services via http access. The URL should have the
following format:
format—http://<server path>/msmdpump.dll
example—http://server01/olap/msmdpump.dll
Database Enter the name of the Analysis Services database to which you want to connect.
Username Enter the user name for the user account to be used in this connection.
Password Enter the password for the user account specified in Username.
Category (Optional) Select an existing category or create a new one.
Note: In NoSQL and Business Intelligence connections, Toad automatically saves the password in the
connections.xml file as obfuscated text, as well as in Toad. To add additional password security, use
Toad's Master Password feature.
4. Click Connect to connect immediately and also save the connection information. Optionally, you can click
Save to save the connection without connecting.
5. Upon creating an initial connection, Toad automatically maps the data source objects. This process
runs in the background, and until it is finished, you may experience a delay when attempting to access
these objects.
Tips:
l Connections are stored in the connections.xml file and can be found by clicking the Application Data
Directory link in Help | About.
l You can specify a proxy server to use for Business Intelligence and NoSQL connections at Tools | Options
| Database | Data Services.
2. Select SAP ASE, SAP IQ, or SAP SQL Anywhere from the Group list.
3. Enter the login information. Review the following for additional information:
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.
4. Click Connect to connect immediately while saving the connection information. Optionally, click Save to
save the connection without connecting.
Note: An SAP HANA ODBC driver is installed along with Toad Data Studio and is required if using a HANA
connection in a cross-connection query.
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory
link in Help | About.
Login
Server name Enter the name of the server hosting the database to which you want to connect.
Use Single Sign Select if the user is using a single sign-on authentication system.
On
Password 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.
Session mode Displays the session mode, which is always Teradata in a Toad Teradata
connection.
Default database (Optional) Enter a default Teradata database for the connection.
Category (Optional) Select an existing category or create a new one.
Advanced
Mechanism (Optional) Select an authentication mechanism from the list.
Parameter (Optional) Enter the parameters required by the selected authentication
mechanism. See your system administrator for these values.
Account string (Optional) Enter a new account string.
Character set Select a character set.
Note: When querying or viewing data in a column defined with GRAPHIC or
CHARACTER SET GRAPHIC data type, you must specify a Character set of UTF-
16 for the session.
Use data Select if using data encryption.
encryption
Response buffer Specify a Response Buffer Size (in bytes). This allows you to govern the number of
size rows returned in a single response. To increase the number of rows per response,
increase the response buffer size. This strategy might help to improve performance
with larger data sets.
The default value in Toad is set to the maximum, 1040000 bytes.
4. Click Connect to connect immediately while saving the connection information. Optionally, click Save to
save the connection without connecting.
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory
link in Help | About.
Other Issues
Issue Cause/Solution
A delay occurs between writing a value to a This delay is the default when you are writing and reading data
database via one connection and seeing between two different Jet connections. The delay occurs even if the
the updated value via another connection. two connections reside in the same client process.
Solution:
Use a single connection when updating data.
Username Enter the user name to use for this connection in the following format:
user@REALM or domain\user
Hive host realm Enter the Kerberos realm of the HiveServer2 host.
Hive host FQDN Enter the fully-qualified domain name (FQDN) of the HiveServer2 host.
Note: If necessary, contact your IT department to obtain this information.
Service name Enter the service name of the Hive server. The default is hive.
Note: Please contact your Kerberos/IT administrator for more info on your userid and host name
Before you can successfully connect to Hive using Kerberos authentication, the Toad client computer must have a
Kerberos Key Distribution Center (KDC) address entry for the Hive host realm. To define the KDC entry, use the
following procedure.
You only need to run this command once for the given realm. To confirm the setting, enter the following command:
ksetup. This command should return both the name of the Hive host realm and the KDC name you specified.
Open a Windows Command Prompt as Administrator and enter the following command:
ksetup /addkdc <REALM> <KDC name>
Where <REALM> is the name of the Hive host realm and <KDC name> is the DNS name of the computer running
the KDC service for the given realm. ksetup is the Kerberos setup tool in Windows.
Run the command ksetup again to confirm the realm has been added.
Enter “port” in the filter search box to know the hive transport mode and port configuration in this Hive server.
If hive.server2.transport == HTTP, then check “http mode” in Toad, and port number in Toad should use
‘hive.server2.thrift.http.port’.
If hive.server2.transport == binary, then uncheck “http mode” in Toad, and port number in Toad Data Studio should
use “HiveServer2 Port”.
Note: HDP does not use SSL when Kerberos authentication is enabled.
Cloudera
Enter “Port” in the search box to check the HiveServer2 Port in CDH because CDH does not support using the Thrift
HTTP mode to connect to HiveServer2.
Excel Connections
Issue Cause/Solution
Tables are limited to 256 This is a known limitation with Excel worksheets.
columns and 65536 rows.
Column names longer than 64 This is a known limitation with Excel worksheets.
characters are truncated and
the remaining characters
display as null.
Columns that include text When you connect to Excel, the driver automatically scans the first eight rows
values or special characters as in a column and applies the data type used in a majority of those rows to all
Installation Issues
The following table describes issues related to installing Toad for DB2.
Connection Issues
Issue Cause/Solution
ERROR [08001] [IBM] SQL1336N The You are attempting to connect to a database version that is not
remote host was not found. supported in Toad.
SQLSTATE=08001 Solution:
Review the list of supported databases in the Release Notes or
Installation Guide.
ERROR [58031] [IBM] SQL1031N The Catalog entries have not been imported or defined for the
database directory cannot be found on the connection.
indicated file system. SQLSTATE=58031 Solution:
See "Configure DB2 Client Connections" on page 28 for more
information to determine the best method for cataloging a
database.
"The type initializer for A settings file might be corrupt.
'IBM.Data.DB2.DB2Connection' threw an Solution:
exception."
Rename your local settings directory so a new one can be
or
recreated.
"SUCCESS - unable to allocate an
environment handle."
To rename your local setting directory
1. Exit Toad.
2. Navigate to the following settings directory:
Other Issues
Issue Cause/Solution
Unable to capture Container Information in Certain Toad functions require that the DFT_MON_BUFPOOL
DB2 for LUW Multi-Partition Databases database manager configuration parameter be set to ON to
capture information on containers used in DB2 for LUW databases.
Additionally, to capture container information across all partitions in
a multi-partition database, the snapshot monitor requires that all
database partitions be active. To activate all database partitions
(and keep them active), execute the DB2 command ACTIVATE
DATABASE real_database_name on the server before connecting
Toad to the database. See your IBM DB2 for Linux, Unix, and
Windows documentation for more information about this command.
Installation Issues
Issue Cause/Solution
Error: "Could not load file or assembly You installed a commercial version of Toad for DB2 after
'IBM.Data.DB2.9.1.0, Version=9.1.0.2, uninstalling the freeware version.
Culture=neutral, Solution:
PublicKeyToken=7c307b91aa13d208' or
You must remove run time information for the freeware version of
one of its dependencies. The system
Toad from the .NET system.config file.
cannot find the file specified."
Connection Issues
Issue Cause/Solution
ERROR [08001] [IBM] SQL1336N The You are attempting to connect to a database version that is not
remote host was not found. supported in Toad.
SQLSTATE=08001 Solution:
Review the list of supported databases in the Release Notes or
Installation Guide.
ERROR [58031] [IBM] SQL1031N The You do not have any catalog entries defined for the connection.
database directory cannot be found on the Solution:
indicated file system. SQLSTATE=58031
See "Configure DB2 Client Connections" on page 28 for more
information to determine the best method for cataloging a
database.
ERROR [42501] [IBM][DB2] SQL0551N You do not have SYSADM privileges for the DB2 for z/OS
"UserName" does not have the privilege to subsystem.
perform operation "SELECT" on object Solution:
"SYSIBM.SYSSTMT". SQLSTATE=42501
Ensure that you are granted SELECT permissions on the DB2
catalog tables.
ERROR [] [IBM] SQL1460N The When using the Time-Sharing Option (TSO) to connect, the user
environment variable "SOCKS_NS" ID, port number, or IP address entered may be incorrect.
required for SOCKS server name resolution Solution:
is not defined or not valid.
Ensure that you use the following for TSO connections:
l DB2 user ID for the DB2 subsystem
l Port number that DB2 listens on, for remote connections,
via the DB2 DDF address space
l IP address for the z/OS subsystem
ERROR [56038] [IBM][DB2] SQL0969N In general, Toad does not support a z/OS subsystem running in
There is no message text corresponding to Compatibility mode.
SQL error "-4700" in the message file on Solution:
this workstation.' when connecting to
If possible, switch the subsystem's operating mode to Full Function
compatibility mode database.
mode.
-or-
If this is not possible, Toad now provides a message when you
After connecting, some objects do not connect to subsystem, informing you of that the subsystem is
display properly or some functionality does running in compatibility mode and that some features might not be
not work as designed. available.
Other Issues
Issue Cause/Solution
Poor performance when browsing DB2 for User-defined indexes on specific system catalog tables can
z/OS objects in Toad. Indexes are improve performance when you are browsing DB2 for z/OS objects
populated slowly. in Toad. The following link contains the DDL for indexes that can
optimize Toad performance on your DB2 for z/OS subsystem.
Keep in mind that the creation of these indexes is a
recommendation only. The indexes can have different results in
different environments, depending on the number of DB2 objects
and the amount of data involved. To create these indexes, edit and
run the DDL contained in the following file:
ToadDB2zOSIndexes.txt
Additionally, if the schema drop-down lists in the Object Migration
wizard populate slowly, consider creating an index on the
SCHEMA and CREATOR columns in the catalog table for each
object type. Here is a list of some of the object-type tables:
SYSIBM.SYSSYNONYMS
SYSIBM.SYSSEQUENCES
SYSIBM.SYSROUTINES
SYSIBM.SYSTABLES
SYSIBM.SYSDATATYPES
SYSIBM.SYSINDEXES
SYSIBM.SYSTRIGGERS
SYSIBM.INDEXES
Encountering the S378 Abend when This issue appears because the Toad z/OS Component tries to
running IBM DB2 z/10 subsystem in reference the QUEST.QC200ZPARM function.
Conversion mode with older versions of Solution:
Toad.
DROP the QUEST.QC200ZPARM function from your DB2 z/OS 10
subsystem. This will eliminate the possibility of the function being
called into the WLM environment procedure and causing the S378
Issue Cause/Solution
Unable to view all available databases. The InformixODBC driver does not return information about every
available database.
Connection Issues
Issue Cause/Solution
"InvalidCastException" error when This is a known issue in MySQL.
connecting to MYSQL 4.1.14-nt database Solution:
Review the known issue and download a patch from:
http://bugs.mysql.com/bug.php?id=12771
"System.IO.DirectoryNot Solution:
FoundException"error occurs each time
you attempt to connect after installing Toad 1. Exit Toad.
into a directory other than the default 2. Locate the MySQL.xml file in the C:\Documents and
directory. Settings\username\Local Settings\ Application Data\Quest
Software\ Toad for MySQLversion\ ModuleSettings
3. Rename or delete the MySQL.xml file.
4. Restart Toad.
Connection Issues
Review the following to help troubleshoot Oracle:
Issue Cause/Solution
Attempting to connect when Oracle Instant Solution:
Client is installed results in a In order to connect using the Oracle Instant Client, the directory for
System.NullReferenceException error the Instant Client must be included in the environmental path, or
you must copy the client files for the instance to the root install
directory of Toad Data Studio.
You can also connect to the database without using an Oracle
client or TNSNames file by selecting the Direct tab in the Create
New Connection window.
An error occurs when attempting to connect Toad does not support Oracle Rdb at this time.
to Oracle Rdb using an ODBC driver
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
Connection Issues
Issue Cause/Solution
Unable to connect to the database. The Stored procedures that the ODBC driver requires currently do not
following message displays: "The exist on the server.
ODBCMDA procedures have not been Solution:
installed on this database..."
Install the required procedures.
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.
Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT
landscape. From database and systems management, to Active Directory and Office 365 management, and cyber
security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000
companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the
next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat.
Quest Software. Where next meets now. For more information, visit www.quest.com.
Contact Quest
For sales or other inquiries, visit www.quest.com/contact.
H S
Hive Salesforce.com
create connections 42 create connections 53
server virtualization 10
I
SharePoint
Informix, troubleshoot 76
create connections 38
install 12
shortcut keys
Citrix 18
configure to match other applications 19
Citrix support 10
silent install 14
client requirements 6
prerequisites 15
silent 14
Snowflake
L create connections 55
LDAP SQL Azure
DB2 support 33 create connections 57
Oracle support 47 SQL Server
look and feel configuration 19 create connections 57
M troubleshoot 78
SQL Server Analysis Services
MySQL
create connections 61
create connections 44
Sybase
troubleshoot 76
create connections 62
O
system requirements 6
OBIEE
T
create connections 50
Teradata
ODBC
create connections 64
create connections 45
Toad, customize 19
Oracle
troubleshoot
OBIEE, create connections 50
DB2 LUW connections 71
Oracle, create connections 47
DB2 z/OS connections 73
troubleshoot 77
Excel 69
Informix issues 76
MySQL 76
U
uninstall 19
V
virtualization support 10