Toad For Data Analysts 3.1: Installation Guide

Toad for Data Analysts 3.
1
Installation Guide
2012 Quest Software, Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchasers personal use without the written permission of Quest Software, Inc. The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 www.quest.com email: [email protected] Refer to our web site for regional and international office information. Trademarks Quest, Quest Software, the Quest Software logo, Benchmark Factory, Toad, T.O.A.D., Toad World, and vToad are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Softwares trademarks, please see http://www.quest.com/legal/trademark-information.aspx. Other trademarks and registered trademarks used in this guide are property of their respective owners. Toad for Data Analysts 3.1 Installation Guide February 29, 2012
Table of Contents
Installation System Requirements
Client Requirements Server Requirements Virtualization Support User Requirements
7 7
7 9 12 12
Install Toad Specify Application Data Directory Location Read-Only Installation Install Toad Silently
Determine Which Installer to Use Silent Installation Prerequisites Silent Installation Using the Executable Silent Installation Using the Microsoft Installer
14 14 16 17
17 18 18 20
Install Toad on Citrix Systems Upgrade Toad Files Migrated During Upgrades Uninstall Toad Register Toad Configure Toad Layouts Create Connections Understand Toad Connections
Share Database Connections
24 25 25 27 28 28 32 32
32
Configure Oracle LDAP Support Create Oracle Connections

Configure the Oracle Instant Client
33 34
35
Toad for Data Analysts Installation Guide Table of Contents
Create an Oracle Connection
35
Create Oracle Business Intelligence Connections Configure DB2 Client Connections

Define DB2 Client Connections Maintain DB2 Client Connections
37 39
39 47
Configure DB2 LDAP Support Create Toad Connection Profiles for DB2
Create Connection Profiles Manage Connections
49 50
51 53
Create Access Connections Create Business Objects Connections Create Excel Connections Create MySQL Connections Create ODBC Connections Create Salesforce.com Connections Create SQL Server and SQLAzure Connections Create Sybase Connections Create Teradata Connections Troubleshoot Connections Troubleshoot Access Issues
Missing Functionality and Object Information Other Issues
54 55 57 60 61 63 64 67 68 71 71
71 71
Troubleshoot Excel Issues

Excel Connections Opening Excel Files in Toad Document Window
71
72 74
Troubleshoot DB2 LUW Issues

Installation Issues
74
74
Connection Issues Other Issues
76 77
Troubleshoot DB2 z/OS Issues

Installation Issues Connection Issues Missing Functionality or Object Information Other Issues
78
78 79 80 81
Troubleshoot Informix Issues Troubleshoot MySQL Issues

Connection Issues Missing Functionality or Object Information
82 82
82 83
Troubleshoot Oracle Issues

Connection Issues Missing Functionality and Object Information
84
84 84
Troubleshoot SQL Server Issues Troubleshoot Sybase Issues

Connection Issues Missing Functionality or Object Information Other Issues
85 86
87 87 87
Configure Version Control About Version Control

Prerequisites
88 88
88
Configure TFS or VSS Configure CVS Configure Subversion Troubleshoot Version Control
Troubleshoot Upgrades Troubleshoot Other Issues
89 91 93 95
95 95
Appendix: Contact Quest Contact Quest Support

Toad Community
97 97
97
Contact Quest Software About Quest Software Index
97 98 99
1
Installation
System Requirements
Client Requirements
Before installing Toad, ensure that your client system meets the following minimum hardware and software requirements: Platform Memory 1 GHz Processor (recommended minimum) 512 MB of RAM minimum, 1 GB recommended Note:The memory required may vary based on the following:
l l l l
Applications that are running on your system when using Toad Size and complexity of the database Amount of database activity Number of concurrent users accessing the database
Hard Disk Space
1.33 GB to install Toad 475 MB to run Toad Professional edition, 350 MB to run Toad Base edition Note: The disk space required may vary based on the edition of Toad selected for installation.
Operating System
Windows Server 2003 Windows XP Professional (32-bit or 64-bit) Windows Vista (32-bit or 64-bit) Windows Server 2008 (32-bit or 64-bit) Windows 7 (32-bit or 64-bit)
.NET Framework
Microsoft .NET Framework 3.5 (Service Pack 1) Note:The following conditions apply:
l
If you have the .NETFramework 4.0 installed, you must still install the .NET Framework 3.5 (Service Pack 1). The .NET Framework Client Profile is not supported. To run Toad, the .NET security policy must be set to unrestricted. See "User Requirements and Restrictions for Running Toad " for more information.
l l
Toad for Data Analysts Installation Guide Installation
Teradata .NET Data Provider You must install the Teradata .NET Data Provider (13.10 or later) to use a Teradata native connection in Toad. Note: To use a Teradata connection in a cross-connection query, you must also install a Teradata (13.10 or later) ODBC driver. Database Client Existing DB2 Client Support (DB2 native provider only) Toad installs a DB2 9.7 (Fix Pack 4) client as part of the installation process. The DB2 9.7 client can co-exist with an existing DB2 8 client, but is incompatible with a DB2 7 client. If a DB2 7 client already exists on your computer, the Toad installation stops and cannot complete. To resolve, first upgrade to the DB2 8 client. Then restart the Toad installation to avoid losing functionality in some DB2 native tools. Existing 64-bit DB2 Client (DB2 native provider only) If you have a 64-bit DB2 client installed, you must install Toad using the ToadforDataAnalysts_64bit_Client.exe. Oracle Client Toad can connect to Oracle using Direct Connect (no need for an Oracle Client) or can connect using an Oracle Client or Oracle Instant Client. However, if you want to use LDAP, you must install an Oracle Client. Toad supports 9i or later Oracle Clients and Oracle Instant Clients. Notes:
l
You cannot use Oracle Direct Connection in a crossconnection query. To use an Oracle connection in a cross-connection query, you must install an Oracle Client (full install) or you must install the Oracle Instant Client plus the Oracle ODBC driver.
Additional Requirements
Web Browser Microsoft Internet Explorer 6.0 or later Spatial Data Types To work with spatial data types used in SQL Server 2008, you must install SQL Server 2008 Client Tools or SQL Server Management Studio 2008.
Server Requirements
Before installing Toad, ensure that your server meets the following minimum hardware and software requirements: Operating System Oracle Native Database Provider IBM AIX 5.1, 5.2, 5.3 HP-UX 11i 1.5, 2 (32-bit or 64-bit) Red Hat Enterprise Linux AS release 3 and 4 (32-bit or 64-bit) Solaris 7, 8, 9, 10 (32-bit or 64-bit) SuSE 7, 8, 9 Windows 2003 (32-bit or 64-bit) Windows XP SQL Server Native Database Provider Windows Server 2000 Service Pack 4 or later Windows 2000 Professional Edition Service Pack 4 or later Windows XP (32-bit with Service Pack 2 or later and 64-bit) Windows Server 2003 (32-bit or 64-bit) Service Pack 1 or later Windows Vista (32-bit or 64-bit) Windows Server 2008 (32-bit or 64-bit) Windows Server 2008 R2 (64-bit) Windows 7 (32-bit or 64-bit) DB2 for z/OS Native Database Provider z/OS (V1R6 Base Services [5694-A01] or later) DB2 for LUW Native Database Provider IBM AIX 5.1, 5.2, 5.3, 6.1 HP-UX 11i 1.5, 2 (32-bit or 64-bit) Red Hat Enterprise Linux AS release 3 and 4 (32-bit or 64-bit) Solaris 7, 8, 9, 10 (32-bit or 64-bit) SuSE 7, 8, 9 Windows 2000, 2003 (including 64-bit), 2008, XP, Vista, Windows 7 MySQL Native Database Provider Windows 2003 Windows Server 2000 Service Pack 4 or later Windows 2000 Professional Edition Service Pack 4 or later Windows XP (32-bit with Service Pack 2 or later and 64-bit) Windows Server 2003 (32-bit or 64-bit) Service Pack 1 or later Windows Vista (32-bit or 64-bit) Windows Server 2008 (32-bit or 64-bit) Windows Server 2008 R2 (64-bit)
10
Windows 7 (32-bit or 64-bit) Sybase Native Database Provider Windows Server 2000 Service Pack 4 or later Windows 2000 Professional Edition Service Pack 4 or later Windows XP (32-bit with Service Pack 2 or later and 64-bit) Windows Server 2003 (32-bit or 64-bit) Service Pack 1 or later Windows Vista (32-bit or 64-bit) Windows Server 2008 (32-bit or 64-bit) Windows Server 2008 R2 (64-bit) Windows 7 (32-bit or 64-bit) Native Database Server Toad supports the following databases: Oracle 9i, 10g, 11g, 11g R2 Toad has been tested on Oracle Exadata 2.0 running Oracle database 11g R2. SQL Server 2000 (Service Pack 3 or later) 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 Note:SQL Server Compact Edition is not supported. IBM DB2 for LUW 8.1.5 or later IBM DB2 for LUW 9.1 or later IBM DB2 for z/OS 8 IBM DB2 for z/OS 9 IBM DB2 for z/OS 10 Notes:
l
To run RUNSTATS and the native REORG utility on tablespaces and indexes in DB2 for LUW, Toad supports DB2 for LUW 8.2.2 or later. Toad may support IBM DB2 Express and SWE in addition to listed above servers, but note that no testing was performed on it. Toad supports DB2 8 for z/OS running in Full Function mode, but does not support DB2 8 for z/OS running in Compatibility mode.
MySQL 4.1, 5.0, 5.1 Sybase ASE 12.5, 15.0.2, 15.0.3, 15.5 Sybase IQ 15 Sybase SQLAnywhere 12 Teradata 12.0, 13.0, 13.10
11
Access 2003, 2007, 2010 Excel 2003, 2007, 2010 ODBC Database Server Toad for Data Analysts allows you to create a connection to a database that supports an ODBC 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 l l
DB2 for i5/OS V5R4 and IBM i 6.1 Informix Dynamic 10.00, 11.0 (limited testing) Ingres Community Edition 2006 R2 on Windows 32-bit (limited testing) Netezza Data Warehouse Appliance 4.6.6, 6.0 PostgreSQL 8.3.4 Vertica 4.1, 5.0, 5.1 (with 4.0, 4.1 ODBC driver)
l l l
Note: For a list of databases that are not supported, see Known Issues in the Release Notes. Cloud Database Service Oracle databases running on Amazon EC2 SQLAzure Note:To connect to SQLAzure, you must have read access to the master database. SQLServer databases running on Amazon EC2 Toad can manage Amazon RDS and any other cloud or service offering compatible with MySQL. Quest Data Services Premium Connections Toad has been tested with, and supports, the following Business Intelligence / Cloud platforms:
l l
Business Objects XI 3.0, 3.1 Oracle Business Intelligence Enterprise Edition 11g (limited testing, not fully-certified) Salesforce.com
12
Virtualization Support
Application Virtualization Limited testing has been performed for Citrix XenApp 5.0 support on Windows Server 2003. See "Install Toad on Citrix Systems" (page 24) for more information. Desktop Virtualization (VDI) Toad has been tested with Quest vWorkspace 7.0 running on Windows XP Professional 32-bit (Service Pack 2).
Note: Toad may work in virtualization environments other than the ones in which it was tested.
User Requirements
User Requirements to Install Toad Only Windows Administrators and Power Users can install Toad. Note:The following exceptions exist for Power Users:
l
A Power User cannot install Toad on a computer running Windows Vista Enterprise. This is a Windows limitation because Vista does not support Power User mode. (DB2 only) A Power User cannot install Toad if a DB2 for LUW version earlier than 8.1.7 already exists on the computer. Only an Administrator can install Toad under this condition. However, if the computer has an existing DB2 for LUW 8.1.7 or later installation, a Power User can install Toad as long as this user belongs to the DB2ADMNS or DBUSERS group.
If an Administrator installs Toad, the Administrator can share the Toad shortcut icon on the desktop and menu items with any usera Power User, Restricted User, Vista standard user on the computer. If a Power User installs Toad, a Restricted User cannot do the following:
l l
Associate file extensions. View the Toad shortcut icon on the desktop or the Toad menu options in the Windows Start menu. As a workaround, Restricted Users can create a shortcut to Toad from the install directory and place the shortcut on their desktop.
User Requirements and Restrictions for Running Toad The following describes the requirements and restrictions for users who launch and run Toad:
l
(DB2 only) A Windows Power User or Restricted User must belong to the DB2ADMNS or DB2USERS group. To add the user to one of these groups, select Start | Control Panel | Administrative Tools | Computer Management | System Tools | Local Users and Groups | Groups | DB2ADMNS or DB2USERS.
13
(DB2 only) A Windows Vista user must be either an administrator or a standard user that belongs to an Vista Administrators group. Additionally, to enable full functionality in Toad when Vistas User Access Control security feature is turned on, the standard user must run Toad as an administrator. (Right-click the Toad icon on the Vista desktop and select Run as administrator.) (DB2 only) A Windows Power User or Restricted User does not have the authority to add or remove DB2 catalog entries using the Toad Client Configuration wizard. However, these users can use the Import Profile function in the Toad Client Configuration wizard to import catalog entries to Toad. (DB2 only) To take full advantage of Toad for DB2 LUW functionality, the user ID specified in the Toad connection profile for each DB2 for LUW database connection requires the authorizations listed in the following document: ToadDB2LUWAuthorizations.xls
(DB2 only) As a minimum requirement to manage a DB2 for z/OS subsystem in Toad, the user ID defined in the Toad connection profile for the subsystem must either have SYSADM privileges or SELECT privileges on the DB2 catalog tables. For a complete list of authorizations (and corresponding GRANT statements) a user requires to take full advantage of Toad for DB2 z/OS functionality, refer to the following document: ToadDB2zOSAuthorizations.doc
To run Toad, the .NET security policy must be set to Unrestricted. To modify the security policy: 1. Select Control Panel from the Windows Start menu. 2. Double-click Administrative Tools. 3. Double-click Microsoft .NET Framework version Configuration. 4. Select My Computer, and then select the Runtime Security Policy node. 5. Select Evaluate Assembly from the list of tasks in the right panel, and locate and select Toad.exe in the File field. 6. Click Next and set the permission to Unrestricted.
To create or modify the QuestSoftware.ToadSecurity table to enable Toad Security, the user who maintains this table must have privileges to create, insert, update, and delete it. All other users need only the ability to read the QuestSoftware.ToadSecurity table to use Toad Security features.
14
Install Toad
Starting with 3.1, Toad for Data Analysts is available in three editions: Base, Professional, and Premium. See "Toad for Data Analysts Features" in the online help for more information. Note:If you received Toad for Data Analysts with your purchase of Toad for Oracle, note that by installing Toad for Data Analysts you agree to use the software solely on the seat for which Toad for Oracle was purchased. To install Toad 1. Run the ToadInstaller.exe. Notes:
l
DB2 restricts you from having a DB2 32-bit client and DB2 64-bit client on the same computer. The Toad for Data Analysts regular Installer installs a DB2 32-bit client. If you have a 64-bit environment with a 64-bit DB2 client installed, you must install Toad for Data Analysts using the ToadforDataAnalysts_64bit_Client.exe During installation, you can select to install Toad as Read-only. See "ReadOnly Installation" for more information.
2. Complete the wizard. Note: During installation, if the user overrides the default installation directory location, the directory path cannot contain Unicode characters. This is due to the fact that we install a DB2 LUW client in the user specified Toad Installation directory and the DB2 installation does not support such characters.
Specify Application Data Directory Location

Toad for Data Analysts 3.1 stores settings files in the user's Application Data directory. The default location cannot be modified from within the application. Toad provides two methods to change the default location: by using a Registry setting or by using a command switch in a Toad shortcut. Use the Registry setting method to change the application data directory from Roaming to Local. Use the command switch method to change the location to any new path. To change Toad Application Data directory location from Roaming to Local In the Registry under Toad for Data Analysts (Computer\HKEY_CURRENT_ USER\Software\Quest Software\Toad for Data Analysts\3.1), add LOCALSETTINGS with a value of 1.
15
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. Operating System Windows XP Default Location New Location when LOCALSETTINGS = 1 C:\Documents and Settings\<user>\Local settings\Application Data\Quest Software\Toad for Data Analysts 3.1 C:\Users\<user>\AppData\Local\Quest Software\Toad for Data Analysts 3.1
C:\Documents and Settings\<user>\Application Data\Quest Software\Toad for Data Analysts 3.1 C:\Users\<user>\AppData\Roaming\Quest Software\Toad for Data Analysts 3.1
Windows 7
To change Toad Application Data directory location using a command-line switch You can override the default Application Data directory by running toad with the command switch: Toad.exe --datadir="YourNewDirPath" To instruct Toad to always use the new directory path, add the command switch and the new directory path to a Toad desktop shortcut. Then use the desktop shortcut when opening Toad. 1. To add the command switch, right-click the Toad shortcut and select Properties. 2. Enter the command switch and add the directory path in quotes (replace "YourNewDirPath" with your directory path).
16
Read-Only Installation
During installation, you can select an option to install Toad as a read-only application. This lets you query data and view objects using Toad, but all actions that can impact the database (Create, Alter, Drop, Insert, Update, etc.,) are disabled or hidden. This ensures that you can use Toad without worrying about committing a change to a sensitive production instance. The following image shows an example of the differences between a typical and a read-only installation:
17
To install a read-only version of Toad for Data Analysts 1. During installation, select the Read-only option.
To change an existing installation to read-only 1. Reinstall Toad and select Read-only Install on the Install Type page.
Install Toad Silently

Silent installation provides a convenient method for deploying Toad to multiple machines. With some customization, you can also deploy the license key and settings at the same time. Note:
Determine Which Installer to Use

Before performing a silent installation, review the following to determine which installer to use: Installer Executable file (.exe) Advantages Silent installation using the .exe file has the following advantages:
l
Disadvantages Silent installation using the .exe file has the following disadvantages:
l
Verifies whether the prerequisite software is installed, and if not, redirects you to the download location.
Cannot deploy custom Toad settings files or license keys. Installer automatically exits if the prerequisite software is not installed.
Microsoft Installer file (.msi)
Supports deployment of Toad settings files and license keys.
Silent installation using the .msi file has the following disadvantages:
18
Installer
Advantages
Disadvantages
l
Requires manual verification and download of any prerequisite software. Requires a manual uninstall of the previous version of Toad using Add/Remove Programs.
Silent Installation Prerequisites

Before you perform a silent installation, you must install the following software on every computer where you are installing Toad:
l l
Microsoft .NET Framework 3.5 (Service Pack 1) (DB2 native provider only) Toad installs a DB2 9.7 client as part of the installation process. The DB2 9.7 client can co-exist with an existing DB2 8 client, but is incompatible with a DB2 7 client. If a DB2 7 client already exists on your computer, the Toad installation stops and cannot complete. To resolve, first upgrade to the DB2 8 client. Then restart the Toad installation to avoid losing functionality in some DB2 native tools.
Silent Installation Using the Executable

Use the executable file to perform a silent install to the default directory (or to a different directory) and to specify options such as logging installation messages. To perform a silent install using the executable file 1. At a Windows command prompt, switch to the drive or directory where the executable for Toad is located. (This file can be downloaded from the Quest web site or can be found on the Toad installation CD-ROM.) 2. For a standard installation with all features enabled, enter the following command:
ToadInstaller.exe /S
For a read-only installation with create, alter, and drop functionality disabled, enter the following command:
ToadInstaller.exe /S READONLY=TRUE
You can customize MSIEXEC command-line options and overrides for your
19
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 /L C:\temp\ installLog.txt Description (Optional) Write installation messages to the specified log. You can append other options, such as x for debug (used in the previous example) or v for a verbose log. See the log section at http://msdn2.microsoft.com/enus/library/aa367988.aspx for more information about additional logging options. Also, 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. Toad Default Installation Option Overrides You can specify the following values to override Toads default installation options. Enclose each value in double quotations. Option INSTALLDIR Description (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 for Data Analysts 3.1. (Optional) Specify one of the following:
l
ALLUSERS
For a per-machine installation, specify 1. This value allows any user to use the Toad shortcut on the desktop after the installation completes. 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.
20
Option
Description 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. 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. If ALLUSERS is 1, the USERNAME value is ignored during installation.
COMPANYNAME
(Optional) Specify the name of the company that owns this installation.
Notes:
l l
All default installation option overrides are case-sensitive. Enclose all values (except for the ALLUSERS value) in double quotations.
Silent Installation Using the Microsoft Installer

Create Transform (MST)Files You can create a Microsoft transform (.mst) file that deploys the license key, custom settings, and connections for users when performing a silent install using the .msi file. You can also use the .msi file to perform a basic silent install using the default directory (or install to a different directory) and to specify command-line options and default installation overrides. See "Perform Silent Installation Using MSI" (page 22) for more information if you are not creating a transform file. Note:(MSI installs on Windows Vista and 7) If you are using MSIto install Toad on Windows Vista or 7 with UAC enabled, you can install a file that adds a "Run as administrator" option when right-clicking the MSI file:http://www.symantec.com/connect/downloads/msi-run-administrator-context-menu-vista. Note: The installer does not verify that system requirements have been met before installing. If you do not want to manually verify system requirements, you should use the .exe file for the silent install.
21
The following procedure uses the Wise Installer to create the transform file. To create a transform file that includes custom Toad settings 1. Save and install the ToadInstaller.msi file on a computer where the Wise for Windows Installer is installed. After customizing Toad settings, you will use the Wise Installer to create the transform file. 2. Open Notepad, and do the following: a. Enter the license key in the first line. b. Enter the site message in the second line. The file should look similar to the following: AAABBBBCCCCCCEDXDWLMV0WJ9-123-45678-B2 Quest Software c. Save the file with license.key as the file name in the Toad install directory. Make sure the file extension is .key not .txt. 3. Launch Toad. The application should open without prompting you to enter a license key. 4. Select Tools | Configuration Wizard from the Toad menu and complete the Configuration wizard. This wizard creates an initial settings file (Settings.xml). 5. Select Tools | Options from the menu in Toad to open the Options window. 6. Select each page in the window and set any options you want to deploy. These options create a module settings folder and files. 7. Select View | Connection Manager from the menu in Toad to open the Connection Manager. 8. Create any connections you want to deploy. 9. Exit Toad. Upon exiting, a Connections file is created. 10. Create the Microsoft Transform file, using any appropriate tool. The following steps describe how to use the Wise for Windows Installer to create the file. a. Select File |New. b. Select Custom Templates under Categories, and then select the Transform template in the New Installation File window. c. Select the ToadInstaller.msi file in the Select the .MSI file to base this transform on window. d. Save the project. e. Select Files from the Feature Details view.
22
f. Locate the following files and click Add to add them to the project: File to Add Settings.xml Location This file is located in the following directory: C:\Documents and Settings\username\Application Data\Quest Software\ Toad for Data Analysts 3.1. This folder and related files are located in the following directory: C:\Documents and Settings\username\Application Data\Quest Software\ Toad for Data Analysts 3.1\ModuleSettings. This file is located in the following directory: C:\Documents and Settings\username\Application Data\Quest Software\Toad for Data Analysts 3.1.
ModuleSettings folder and files
Connections.xml
g. Save the project and compile it to create the transform (MST)file. 11. Perform a silent install. See "Perform Silent Installation Using MSI" (page 22) for more information. Perform Silent Installation Using MSI To perform a silent install using msi 1. At a Windows command prompt, switch to the drive or directory where the msi installer for Toad is located. 2. For a standard installation with all features enabled, enter the following command:
msiexec /i ToadInstaller.msi /q
For a read-only installation with create, alter, and drop functionality disabled, enter the following command:
msiexec /i ToadInstaller.msi /q READONLY=TRUE
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
23
Command-Line Options The following MSIEXEC command-line options are used in this example: Option /i /q Description Run the installation. 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.aspxfor a complete list of command-line options. Toad Default Installation Option Overrides You can specify the following values to override Toads default installation options. Enclose each value in double quotations. Option INSTALLDIR Description (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 for Data Analysts 3.1. (Optional) Specify one of the following:
l
ALLUSERS
For a per-machine installation, specify 1. This value allows any user to use the Toad shortcut on the desktop after the installation completes. 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
24
Option
Description 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. If ALLUSERS is 1, the USERNAME value is ignored during installation.
COMPANYNAME
(Optional) Specify the name of the company that owns this installation.
Notes:
l l
All default installation option overrides are case-sensitive. Enclose all values (except for the ALLUSERS value) in double quotations.
Note: During installation, if the user overrides the default installation directory location, the directory path cannot contain Unicode characters. This is due to the fact that we install a DB2 LUW client in the user specified Toad Installation directory and the DB2 installation does not support such characters.
Install Toad on Citrix Systems

Toad must be installed on the Citrix server by the Citrix administrator. Users then connect to this instance through their Citrix login. Note: Limited testing has been performed for Citrix XenApp 5.0 support on Windows Server 2003. To install Toad on a Citrix system 1. Connect to the Citrix Environment as an administrator. 2. Copy Toad to the Citrix server, if needed. 3. Start the Toad installation process. 4. During installation, select the Anyone who uses this computer checkbox when prompted.
25
5. Repeat steps 2 through 4 for each server in the Citrix farm. Note: Although you must install Toad on every server in the Citrix farm, you only need to publish Toad once. 6. Review the following considerations regarding licensing:
l
A license supplied by an administrator always overrides a user-supplied license in a Citrix environment. If you need to provide the same Toad functionality to all users, you can enter the default license key for all users.
Upgrade Toad
To upgrade Toad 1. Run the ToadInstaller.exe installation program from the DVD or downloaded file. 2. Select Uninstall Toad and continue with install. 3. Complete the wizard. If you are upgrading from a previous version of Toad, you are prompted to migrate your settings the first time you start Toad. The settings files include database connections, layout customizations, shortcut keys, and options customized in the Options pages. To migrate the settings again, remove or rename the current version's Application Data folder and migrate the files from the previous version's Application Data folder.
Files Migrated During Upgrades

When upgrading to a new version of Toad, the following files can be migrated from the previous version's Application Data Directory (click the Application Data Directory link in Help |About to open the directory). 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 Action.log Description Tracks your usage within Toad. If you agree to share this data, the file is automatically sent to Quest on a periodic basis. Contains all connections stored in the Navigation Manager or the New Connection window. Contains the SQL Output connection trace log file if you select Tools | Execution Trace from the menu.
Connections.xml
ConnectionTrace.log
26
ExceptionTrace.log
Contains a log of all exceptions encountered while running Toad. Contains a log of exceptions encountered when attempting to connect to FTPservers. Contains connections to FTP servers stored in the FTPConnections window. 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. Contains many of the global configuration settings. Used to generate SQL Server execution plans. Contains the last support bundle you generated. Description Used by automation when executing automation scripts.
FTPConnection.log
FTPConnections.xml
Quest.PersistentCache.xml
Settings.xml SqlServerPlanPrefs.xml ToadSupportBundle.zip Folder Automation (temporary folder) Cache
Used to spool cache database metadata to disk if enabled. The data is in binary format and can always be recreated by fetching it from the database. Contains settings that depend on the context within Toad including the following:
l l
Context
AdapterCustom data editing statements. FilterUnnamed filters defined in the Object Explorer or Database Explorer. Named FilterNamed filters defined in the Object Explorer or Database Explorer. TYPETabs 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. Contains custom keyboard shortcut layouts. Contains layouts for some areas in Toad, such as tool
Keyboard Layouts
27
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 readonly, displays not null indicators, etc. Used by Toad plugin components. Contains desktop configurations, including toolbar customizations and tool window locations. Contains pre-set and user created templates for formatting SQL, and the SQLstatement used to preview formatting changes in the Formatting Options page. Contains the SQL statements saved by SQL Recall. Contains the following templates:
l
Plugins Session
SQLFormatter
SQLRecall Templates
Code TemplatesTemplates used to define default values when creating new objects in the Object Explorer or Database Browser. ScriptsStartup scripts to run when connecting. SnippetsCode Snippet entries. ReportsReport entries.
l l l
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 l l
Any new files you create Any copies of files you make for backup purposes Settings files
You can uninstall Toad for Data Analysts 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 for Data Analysts. To uninstall Toad 1. Run the ToadInstaller.exe. 2. Select Uninstall Toad for Data Analysts only. 3. Complete the wizard.
28
Register Toad
If you received Toad for Data Analysts with your purchase of Toad for Oracle, note that by installing Toad for Data Analysts you agree to use the software solely on the seat for which Toad for Oracle was purchased. To register Toad 1. Select Help | Licensing from the menu (ALT+H+L). 2. Review the following for additional information: Authorization key Site message Enter the license key for Toad.
Enter the site message included with the license key.
Note: For users with an existing license key, your license key will enable the Base edition of Toad for Data Analysts. If you upgrade to the Professional edition, you must request a Professional edition license key.
Configure Toad Layouts

Use the Configuration wizard to customize the look and feel of Toad to match Toad for Oracle, SQL Navigator, or your native database tools. In addition, you can specify some window layout and window grouping options, as well as default windows to open on startup and connection. Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions. To configure Toad layouts 1. Select Tools | Configuration Wizard (ALT+T+F). 2. Complete the wizard. Review the following for additional information: Use this page... Layout and Settings To....
Set one of the following:

l
Toad for Data Analysts 3.0Applies shortcut keys used by Toad for Data Analysts, opens default windows, and adds the Wizard toolbar.
29
Use this page...
To....
Toad for OracleApplies shortcut keys used by Toad for Oracle and automatically opens the Project Manager, Editor, SQL Recall, and Output windows. MS Query AnalyzerApplies shortcut keys used by Query Analyzer and automatically opens the Object Explorer, Code Snippets, and Editor windows. MS Management StudioApplies shortcut keys used by Management Studio and automatically opens the Connection Manager and Editor windows. SQL NavigatorApplies shortcut keys used by SQL Navigator and automatically opens the Navigation Manager, Object Explorer, Editor, and Code Snippets windows. Toad for Data Analysts (Original)Applies shortcut keys used by Toad for Data Analysts, opens default windows, and adds the Document Grouping and Wizard toolbars. CustomApplies shortcut keys used by Toad for Data Analysts, and lets you specify layout settings on the remaining pages.
Tip: You can set or modify individual keyboard shortcuts in Keyboard Options in Tools |Options | Environment |Keyboard. Note: If you select a new layout, you may need to restart Toad to see the changes to the Grouping and Wizard toolbars. Look and Feel Set one of the following:
l
SkinApplies the skin style you select to document windows, tool windows, and modal dialogs. Grid styleApplies the grid style you select to the data grid only.
When selecting an option, the current wizard page, including the sample data grid, provides a preview of the change. Database Explorer Style Quick Guide Specify how objects display in the Object Explorer window.
Display a Quick Start Guide that lets you quickly launch frequently used features and tutorials until you are more familiar with the application. Tips:
30
Use this page...
To....
To view this window at anytime, select View | Quick Guide from the menu. To hide this window when starting Toad, select the Do not show on start up checkbox at the bottom of the Quick Guide window.
Group Documents
Specify the following options:

l
Use document groupsDisplays a Grouping toolbar that categorizes features into logical workgroups. Hide windows per groupDisplays only those windows that are associated with the selected group. For example, if the Query group is selected and a Query Builder window is open, it will be hidden when you select the Report group. Note: Unless the Hide windows per connection checkbox is selected, any connections that have a window open for this group display.
Hide windows per connectionDisplays only those windows for the current connection that are associated with the selected group.
Tip: To hide the Grouping toolbar, select Tools | Customize from the menu, and then clear the Grouping checkbox in the Toolbar tab of the Customize window. Group Document Defaults Select a default window to open for each connection when selecting a group from the Grouping toolbar. Understand
l
Database DiagramEasily identify relationships between tables via foreign keys. Database ExplorerDrill-down to details for each object.
Query
l
Query BuilderQuickly create complex queries and subqueries using a graphical interface. SQL EditorPowerful editor for writing SQL queries and scripts.
Report
l
ExcelAutomatically export query results and open them in Excel.
31
Use this page...
To....
Toad ReportSend query results to the Toad Data Report wizard.
Wizard Bar
Select to display the Wizard bar, a toolbar containing frequentlyused actions for the currently open window. It displays along the bottom of the Toad window. Specify which type of new document to automatically open when a new database connection is created. Specify whether to automatically add files to the Project Manager when saving, executing, or sending the files to a report. This option can help you locate and manage your work.
Connection Documents Additional Settings
2
Create 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:
l
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 (illustrated in the following example).
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. 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:
l
(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
Toad for Data Analysts Installation Guide Create Connections
33
soon as the current operation completes.

l
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.
Configure Oracle LDAP Support

You can create Oracle Lightweight Directory Access Protocol (LDAP) connections when your Oracle client is configured for LDAP. Once the client is configured, Toad retrieves names from your LDAP server and displays them in the Database Name list in the Create New Connection window. Notes:
l l
To connect using LDAP, you must install an Oracle client on the computer. 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" (page 35) for more information.
To configure the Oracle client for LDAP 1. Obtain the LDAP.ORA file from your database administrator. 2. Copy the LDAP.ORA file to the folder where the SQLNET.ORA file for your Oracle client is located. The default folder is: ORACLE_HOME\network\admin 3. Open the SQLNET.ORA file and enter "(LDAP)" as the value for the NAMES.DIRECTORY_PATH as follows: NAMES.DIRECTORY_PATH= (LDAP) Note: If you are using multiple naming methods, add the (LDAP) value to existing parameter values. For example, if you are using both the TNSNAMES and LDAP naming methods, add LDAP to TNSNAMES as follows: NAMES.DIRECTORY_PATH= (TNSNAMES, LDAP) 4. Save the SQLNET.ORA file. 5. Launch Toad and select File | New | Connection. 6. Create an LDAP connection following the procedure in Create Oracle Connections (page 34). In step 3, select a database on the LDAP server from the Database Name list.
34
Create Oracle Connections

You can create a new connection, or connect to an existing connection from the Create New Connection window. See "Troubleshoot Oracle Issues" (page 84) for more information about troubleshooting connection issues. Click here to view a video about creating connections in Toad for Data Analysts Tip:You can configure Toad for Data Analysts to accept connection information from Toad for Oracle. See "Add Connection Parameters to Open from Toad for Oracle" in the online help for more information. You can connect to your database using a native Oracle database provider in Toad using one of the following methods: Connection Method Advantages Disadvantages
Client connection (Client tab)Uses an installed Oracle Client or Oracle Instant Client to establish a connection to the database from Toad.
Supports LDAP (See "Configure Oracle LDAP Support" (page 33) for more information about configuring the Oracle client to use LDAP.) Does not require an Oracle Client to be installed Recommended for connecting to Oracle 8i databases
Requires an Oracle client Note:Toad supports Oracle clients and Oracle Instant clients using version 9i or later.
Direct connection (Direct Connect tab) Uses TCP/IP to connect directly to the database.
Only supports common data types. Some advanced Oracle object types cannot be retrieved when connecting using this method. Does not support LDAP (To connect using LDAP, use the Client Connection method instead.)
Note:Quest recommends using one of the methods described in this table to connect to Oracle rather than an ODBC driver. Because ODBC connectivity is generic, it is not fullfeatured and may not be as robust as the fully exploited native database provider.
35
Configure the Oracle Instant Client

The Oracle Instant client installs only those files needed to connect to your database using OCI. Because this client does not write to the registry (no ORACLE_HOMES) or add to the environmental path, you must manually set environment variables so the client can be used with Toad. To configure the Oracle Instant Client to work with Toad 1. Save the Oracle Instant Client files in any location on the computer where Toad is installed. 2. On your Windows desktop, right-click My Computer and select Properties. 3. Select the Advanced tab and click Environment Variables. 4. Click New under System Variables and complete the following: Variable name PATH Variable Value <Path where Instant Client is installed>;%PATH% For Example:C:\Program Files\OracleInstantClient;%PATH% TNS_ ADMIN Notes:
l
<Path where tnsnames.ora file is installed>
If you are using the Oracle Instant Client, you must also install an Oracle ODBC driver before using this connection in a cross-connection query. (The Oracle Client full install does include an ODBC driver.) You cannot use Oracle Direct Connection in a cross-connection query.
Create an Oracle Connection

To create an Oracle connection 1. Click on the toolbar (ALT+F+N).
2. Select Oracle from the Group list box. 3. Review the following for additional information: Login Tab Database name Description Select the alias to use when connecting. This list displays aliases from LDAP as well as any local tnsnames.ora file. Note: If you do not select a database, Toad uses the ORACLE_
36
SID for the selected home. If an ORACLE_SID value does not exist and you do not specify a database, you cannot connect. 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. Connect as Select whether to connect as either SYSDBA or SYSOPER if you have the appropriate permissions. Otherwise, use the default. Select a schema if you frequently work in a different schema than the one associated with your user name. (Optional) Specify the location of an existing explain plan table to use instead of Toad automatically creating one for you when you execute a statement. This is useful if you do not have necessary permissions to create explain plan tables or want to use an existing table. 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. Select this checkbox if you plan to use Automation to generate reports. Description
Schema
Explain plan table
Category
Save password Oracle Client Tab Current home TNSNames Editor
Modify the Oracle home to use, if needed.
Click this button to edit your local TNSNames file. Tip:You can press CTRL+F to open the Find/Replace window to locate entries in the TNSNames Editor. Pressing F3 locates the next entry that matches your criteria. Click this button to edit SQLNET.ORA parameters. Before editing this file, you should create a backup copy. See SQLNET.ORA Profile Parameters in the Oracle documentation for more information. Description
SQLNET Editor
Direct Tab
37
SID
Enter the ORACLE_SID value for the database. This value is specified in the registry under each installed home. Description
Advanced Tab ODBC driver
If an Oracle Client is installed, the default is the Oracle ODBC driver. If no Oracle Client is installed, the default is the Microsoft Access ODBC driver. Tip:You can specify the ODBC driver to use for all connections for this database provider in Tools |Options |Database | Oracle.
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.
Create Oracle Business Intelligence Connections

Using Quest Data Services connectivity, Toad provides the ability to connect to the presentation layer of Oracle Business Intelligence Enterprise Edition (OBIEE). Note: This feature is only available in the Toad for Data Analysts Premium Edition. To create an Oracle Business Intelligence Enterprise connection 1. Click on the Connections toolbar (ALT+F+N).
2. Select Quest Data Services from the Group list. 3. Select Oracle BI Enterprise from the Connection Type list. 4. Enter the connection information in the Create New Connection dialog. Review the following for additional information: URL Enter the Oracle Business Intelligence Enterprise URL to which you want to connect. Note: You must include the port number in the URL as in the following examples: formathttp://<server path>:<port>/analytics/saw.dll examplehttp://server01.mycompany.com:80/analytics/saw.dll
38
Subject Area
Enter the name of the subject area with which you want to work. 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.
Password
Row Limit
Select a row limit to enforce for query results. default = 500,000
Category
Select an existing category or create a new one.
Note: In Quest Data Services connections, Toad automatically saves the password in the connections.xml file as obfuscated text and in Toad. To add additional password security, use Toad's Master Password feature. 5. Click Connect to save the connection and immediately connect to OBIEE. Note: Click Save to save the connection without connecting. 6. Immediately upon creating an initial new connection, Toad analyzes the tables/dimensions available in the presentation layer and maps them to Toad. When this process is finished (the process may run a few minutes or more), the Table Object Mapping dialog displays. Select the tables to map for this connection and click Execute. Notes:
l
In the Table Object Mapping dialog, you can modify the Mapped Name of a table. This is the name that Toad will display in Object Explorer for this table. You cannot have spaces in a mapped name. After creating the connection, you can click in the Object Explorer toolbar to add or remove tables from the connection's table map.
Important Information about Oracle BI Connections You must incorporate the port into the OBIEE database connection URL in the following format: http://<server name>:<port>/analytics/saw.dll An example URL is http://server01.mycompany.com:80/analytics/saw.dll Considerations and Limitations with Oracle BI Connections Review the following limitations and OBIEE behaviors before using an OBIEE connection.
39
Consideration/Limitation Tables vs OBIEE dimensions
Description What you see represented in Toad as tables are actually OBIEE dimensions in the presentation layer, and they do not have exposed keys. The relationships between the source data are managed in the background by Oracle. After dragging a table to the Query Builder diagram pane, you will notice that there are no key icons to represent key columns and no connectors to represent the relationships between tables. The relationships between tables are managed through the Oracle back end. When you execute a query, the joins between source data are handled by Oracle in the background. So, you do not need to draw a relationship between tables before building a query. Some OBIEE columns may have a sort order configured in the server. When querying this type of configured column using ORDER BY, the resulting order is based on the configured columns sort order. There is a maximum character limit of 255.
Table representation in Query Builder
Using ORDER BY on "sort order" configured columns
Max character limit Tips:

l
Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help |About. You can specify a proxy server to use for Quest Data Services connections at Tools | Options | Database |Quest Data Services. Oracle Business Intelligence connections are read-only.
Configure DB2 Client Connections

Toad requires two phases to set up connections to the DB2 for LUW databases and DB2 for z/OS subsystems that you want Toad to manage.
Define DB2 Client Connections

The first phase is to catalog each of these databases or subsystems on the DB2 client installed with Toad. Toad provides the following methods for cataloging the systems: Transfer an existing catalog from another DB2 client on your computer You can transfer the catalog of an existing DB2 client on your local computer to the new Toad DB2 client during initial setup or at any time later.
40
Transfer a Catalog During Initial Setup

When you first launch Toad after installation, Toad provides an opportunity to transfer the catalog of an existing DB2 client on your local computer to your new Toad DB2 client. (In other words, Toad exports and imports the catalog for you.)
Toad makes this option available only when all of these conditions exist:
l
You are launching Toad for the first time since installation. This installation is a first-time Toad installation on your computer, or it is an upgrade from a previous Toad version already on your computer. Toad detects other DB2 clients installed on your computer. These can include the DB2 clients laid down with other installations.
If you choose not to transfer an existing catalog at this point, you can transfer a catalog later. See "Transfer a Catalog Any Time After Initial Setup" (page 42) for more information. To transfer an existing DB2 catalog 1. Open Toad after installation is complete. 2. If Toad displays the Settings Migration Utility window, select whether to migrate from your previously installed Toad. (These settings include Toad connection profiles.)
l
If you migrate settings, the window showing the option to transfer a catalog displays once the migration completes. If you do not migrate settings, the window showing the option to transfer a catalog displays when you select to create the first connection. If the Settings Migration Utility window does not display, go to step 3.
3. On the window showing the option to transfer a catalog, locate the DB2 Client list, and select the name of the existing DB2 client whose catalog you want to transfer to your newly installed Toad .
41
This list contains all current previously installed DB2 clients on your computer, including the default DB2 client instance and other Toad client installations. 4. Click OK to proceed with the catalog transfer. When the transfer completes, the Connections window displays. The Database alias drop-down list now includes all the DB2 databases and subsystems whose catalog entries you transferred. Note: During the transfer process, DB2 does not automatically export catalog entries for the local DB2 instance and its databases installed on your computer unless these entries already exist in the catalog you are transferring. To include local node entries in your Toad DB2 client catalog, you must manually catalog these databases. 5. Proceed to create Toad connection profiles for the DB2 databases and subsystems whose connection profiles you did not migrate (in step 2). For those profiles you migrated, simply select the connection in the Connections window, and provide the login ID and password to start the connection. See "Create Toad Connection Profiles for DB2" (page 50) for more information.
42
Transfer a Catalog Any Time After Initial Setup

To transfer a catalog any time after initial setup 1. In the Connection Manager or on the Connections window, click in the toolbar.
2. From the DB2 Client list, select the name of the existing DB2 client whose catalog you want to transfer to your newly installed Toad. This list contains all current previously installed DB2 clients on your computer, including the default DB2 client instance and other Toad client installations. 3. Click OK. 4. Create Toad Connection Profiles for DB2 (page 50) for any of the transferred catalog entries as needed. Import a DB2 catalog previously exported to a file Toad provides functionality to import an existing DB2 client catalog to your Toad DB2 client, saving you the effort of manually creating individual catalog entries on the Toad DB2 client. This feature executes the DB2 Connectivity Configuration Import Tool command db2cfimp, which imports an export profile containing the catalog exported the from a local or remote DB2 client or a local Toad DB2 client. Either of these functions export DB2 catalogs:
l
Export Profile feature in the Toad Configuration wizard (for exporting your current Toad DB2 client catalog only). See " Export the catalog for the current DB2 client" (page 48) for more information. DB2 Connectivity Configuration Export Tool Command db2cfexp. For more information, see the following IBM documentation:http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/ com.ibm.db2.udb.doc/core/r0002442.htm.
Note: Do not attempt to manually import catalog entries from the IBM CLP window provided with Toad. If you have any DB2 ODBC entries, db2cfimp will override your existing ODBC system with DSN entries and can cause previously configured DB2 ODBC connections to stop working. To import an exported catalog profile 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.
43
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. 5. Complete the wizard. Once you close the wizard, the Database alias drop-down list in the Connections window includes all the DB2 databases and subsystems whose catalog entries you imported. Note: DB2 does not automatically export catalog entries for the local DB2 instance and its databases on the computer from which the export is run (unless these entries already exist in the catalog). Therefore, the profile you are importing might not include these node entries. To add the missing entries to your Toad DB2 client catalog, you must manually catalog the databases. If these databases are local to your computer, catalog them as remote databases. See "Manually catalog DB2 for LUW databases " (page 43) for more information. 6. Proceed to catalog entries as needed. See "Create Toad Connection Profiles for DB2" (page 50) for more information. Manually catalog DB2 for LUW databases To manually catalog a DB2 for LUW database 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 Toad 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: Add a Host Operating system Description Select the operating system for the server on which the DB2 for LUW instance containing the DB2 database you are cataloging resides. For a list of supported server platforms, see the release notes. Enter the TCP/IP address or the system name for the server on which the DB2 database resides.
Host name
44
Port number
Enter the port number for the server on which the DB2 database resides. Select this checkbox to enable the SOCKS secure protocol to handle TCP traffic for this connection. SOCKS adds an authentication mechanism for additional security. Description
Enable SOCKS security Specify an Instance Node name
Enter a user-defined name for the DB2 instance containing the database you are cataloging. If you selected the node name from the tree on the Welcome page, this information is pre-filled (but you can update it as needed).
Instance name Comment Add a Database Database name Database alias
Enter the real name of the DB2 instance. Enter a descriptive comment for the instance, if needed. Description Enter the real name of the DB2 database. Enter a unique nickname to identify the database on your system. Select the authentication method that is required to connect to the database. Enter the service account name for server's service where the database resides. Note: This option is available only when Kerberos is selected as the authentication method.
Authentication
Target principal
5. Complete the wizard. The Database alias drop-down list in the Connections window shows the alias for the newly cataloged database. To complete the Toad connection setup, you must create a Toad connection profile for the database. See "Create Toad Connection Profiles for DB2" (page 50) for more information.
45
Manually catalog DB2 for z/OS subsystems Note: If you connect directly to a DB2 for z/OS subsystem, you cannot take advantage of Sysplex. If you want to use Sysplex, catalog an entry to a DB2 Connect gateway instead. See "Manually catalog DB2 Connect gateways" (page 46) for more information. To manually catalog a DB2 for z/OS subsystem 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 Toad 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: Add a Host Operating system Host name Description Select z/OS for the server operating system.
Enter the TCP/IP address or the system name for the server on which the DB2 subsystem resides. Enter the port number of the service for the DB2 subsystem.
Port number Enable SOCKS security Add a DB2 Subsystem Location name Database alias
Select this checkbox to enable the SOCKS secure protocol to handle TCP traffic for this connection. SOCKS adds an authentication mechanism for additional security. Description
Enter the location name of the DB2 subsystem as defined during the DB2 installation. Enter a unique, user-defined alias to identify the DB2 subsystem on your system. You can use the same name you used in the previous Location name field, as long as it does not already exist in the list aliases in the Toad DB2 client.
46
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" (page 50) 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. To manually catalog an entry to a DB2 Connect gateway 1. Catalog the DB2 subsystem on the DB2 Connect gateway. See the IBM DB2 for z/OS documentation for more information. 2. In the Connections (or Create New Connection) window in Toad, click Database alias drop-down list to open the Client Configuration wizard. 3. Click Add Catalog Entry. 4. Review the following for additional information: Add a Host Operating system Host name Description Select the operating system for the server on which the DB2 Connect gateway resides. Enter the TCP/IP address or the system name for the server on which the DB2 Connect gateway resides. Enter the port number of the service for the DB2 Connect gateway. Select this checkbox to enable the SOCKS secure protocol to handle TCP traffic for this connection. SOCKS adds an authentication mechanism for additional security. Description beside the
Port number
Enable SOCKS security Specify an Instance Node name
Enter an alias for the user-defined node name you specify in the Instance name field. Enter a user-defined name for the gateway node or use the same value entered in the Node name.
Instance name
47
Note: This name does not point to an actual node on the gateway system, but is needed to continue the cataloging process. Add a Database Database name Description Enter the database alias name for the DB2 subsystem. Note: This alias name must match the alias cataloged on the DB2 Connect gateway. Database alias Enter a unique, user-defined alias for the DB2 Connect gateway. You can use the same alias you used in the previous Database name field, as long as it does not exist in the list of Toad for DB2 aliases. Select the authentication method that matches the method specified for the DB2 subsystem on the DB2 Connect gateway.
Authentication
5. Complete the wizard. The Database alias drop-down list in the Connections window shows the name for the newly cataloged DB2 subsystem. To complete the Toad connection setup, you must create a Toad connection profile for the subsystem. See "Create Toad Connection Profiles for DB2" (page 50) for more information. Note: Toad for DB2 supports LDAP connections. See "Configure DB2 LDAP Support" (page 49) for more information.
Maintain DB2 Client Connections

Additionally, Toad provides functionality to perform the following maintenance on the catalog you set up for the current Toad DB2 client: Edit DB2 catalog entries To edit a DB2 catalog entry 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 Toad DB2 client, select the catalog entry for the DB2 database or subsystem that you want to edit. 3. Click Edit Catalog Entry.
48
4. On the Edit Catalog Entry page, update the catalog properties as needed. For a description of the catalog properties, see the following links:
l
Manually catalog DB2 for LUW databases (page 43) Manually catalog DB2 for z/OS subsystems (page 45) Manually catalog DB2 Connect gateways (page 46)
l l
5. Click Next to open the Catalog Script Review window. 6. Review and modify the script in the preview pane as needed. 7. Click Finish. A message window displays, informing you whether the updates to the catalog entry completed successfully. Remove DB2 catalog entries To remove a DB2 catalog entry 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 Toad 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 for DB2 provides functionality to export your current Toad DB2 client catalog to a file, called an export profile. You can then import this profile to set up the catalog for another Toad DB2 client. To create the export profile containing the current Toad 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 Toad DB2 client), you must manually execute this command. For more information, see the following IBM documentation: http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/ com.ibm.db2.udb.doc/core/r0002442.htm.
49
To export the Toad DB2 client catalog 1. In the Connections (or Create New Connection) window, click Database alias drop-down list. beside the
2. Click Export Profile in the Welcome window of the Client Configuration wizard. (You might need to click 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 Toad DB2 client catalog. 5. Select the type of profile you want to create:
l
this button.)
Template to create a profile used as a template for other DB2 clients (default for exporting a Toad DB2 catalog) Backup to create a profile used to back up a DB2 database instance Maintain to create a profile that contains only database or node information required for updating other instances For more information about these profile types, see the IBM documentation (as cited previously) describing the db2cfexp command.
6. Complete the wizard. A message window displays, informing you whether the export completed successfully. Note: DB2 does not automatically export catalog entries for the local DB2 instance and its databases installed on your computer unless these entries already exist in the catalog you are exporting. If you later import the export catalog to a Toad DB2 client, you must manually catalog the missing local-node databases as remote databases. See "Manually catalog DB2 for LUW databases " (page 43) for more information. After you have set up the catalog on the current Toad DB2 client, you can proceed to the second phase of the Toad connection setup. This phase involves creating Toad connection profiles for the cataloged DB2 databases or subsystems. See "Create Toad Connection Profiles for DB2" (page 50) for more information.
Configure DB2 LDAP Support

You can create DB2 Lightweight Directory Access Protocol (LDAP) connections when the DB2 client installed with Toad is configured for LDAP. Configuring the client consists of enabling LDAP support and specifying the host name and port number of the LDAP server. Once the client is configured, Toad retrieves names from your LDAP server and displays them in the Database Alias list in the Connections window.
50
Notes:
l
You must configure LDAP support for the DB2 client installed with Toad regardless of whether an existing DB2 client on the computer is already configured to support LDAP. Currently, Toad for DB2 supports only the access of DB2 LDAP catalog entries. Toad does not support the management of these entries.
To configure the DB2 client for LDAP 1. Open the Command Window for the DB2 client installed with Toad by selecting Start | All Programs | IBM DB2 | <ToadCom, ToadEval, or ToadFree> | Command Line Tools | Command Window. 2. Enter the following command to enable LDAP support:
db2set DB2_ENABLE_LDAP=YES
3. Enter the following command to specify the TCP/IP host name and port number of the LDAP server:
db2set DB2LDAPHOST=<hostname[:port]>
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 dropdown 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" (page 50) for more information.
Create Toad Connection Profiles for DB2

Toad requires two phases to set up connections to the DB2 for LUW databases and DB2 for z/OS subsystems that you want Toad to manage. Click here to view a video about creating connections in Toad for Data Analysts Tip:Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help |About. The first phase is to catalog each of these databases or subsystems on the DB2 client installed with Toad. See "Configure DB2 Client Connections" (page 39) for more information. The second phase involves creating Toad connection profiles for the cataloged DB2 databases or subsystems. Each profile contains the information that Toad needs to connect to the system, such as the user ID and password, DB2 registry settings, and the default schema.
51
Create Connection Profiles

Use these methods to create Toad connection profiles:
l
Migrate existing connection profiles from another Toadinstallation on your computer (available during initial Toad setup only) When you first launch Toad after installation, Toad provides an opportunity to migrate the settings of an existing Toad installation on your local computer to your new Toad installation. These settings include, among other configuration parameters, the Toad connection profiles defined on the earlier installation. (Toad exports and imports these connection profiles for you.) Toad makes this option available only when both of these conditions exist:
l
You are launching Toad for the first time since installation. Toad detects earlier versions of Toad on your computer.
If you choose not to migrate the connection profiles at this point, you can perform the migration later using the Connection Managers' Import Connections feature. To migrate Toad connection profiles 1. Open Toad after installation is complete. Toad displays the Settings Migration Utility window if the conditions described previously exist. 2. Select the Toad installation whose connection profiles you want to migrate to your new Toad installation, and click Migrate. After the migration completes, Toad provides the option to transfer a local DB2 catalog to your new Toad DB2 client. 3. Select to transfer a DB2 catalog or to manually catalog entries later. See "Configure DB2 Client Connections" (page 39) for more information. Note: The connection profiles you migrated are not usable unless you also transfer the DB2 catalog containing the corresponding entries for these profiles (or until you manually create these catalog entries later). After the catalog transfer is complete, your Toad connection setup is complete for all those connections that have both a catalog entry on the Toad DB2 client and a Toad connection profile. For any connection that does not have a corresponding DB2 catalog entry, create an entry. See "Configure DB2 Client Connections" (page 39) for more information.
l
Import Toad connection profiles previously exported to an XMLfile (See "Export connection profiles to an XML file" (page 53) for more information about exporting a profile that you can later import.)
52
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" (page 39) for more information. To import connection profiles 1. In the Connections (or Create New Connection) window, click toolbar, and select Connection file. on the
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. To create a Toad connection profile for a DB2 database or subsystem 1. In the Connections (or Create New Connection) window, click toolbar (ALT+F+N). 2. Select DB2 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 Toad DB2 client. See "Configure DB2 Client Connections" (page 39) for more information if the alias does not display in the list. Tip: Click to refresh the alias list. Normally, Toad caches the Toad 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 schema/auth ID Category Enter the SET SCHEMA value (DB2 for LUW) or the SET SCHEMA or SET CURRENT SQLID value (DB2 for z/OS) for this connection. Select or create a category if you want to color code on the
53
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 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 XMLfile " (page 51) for more information. To export connection profiles 1. In the Connections (or Create New Connection) window, select the connections whose profiles you want to export. 2. Click on the toolbar, and select Connection file.
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
Import missing connections defined on the Toad client You can import all connection entries currently defined in the Toad DB2 client catalog but missing from your current list of Toad connections.
54
Note: The imported connection entries might be associated with incorrect or missing DB2 catalog or Toad connection profile information, making them currently invalid. To re-instate any of these connections, you might need to provide accurate DB2 catalog and Toad profile information. To import missing connections
l
In the Connections or Connections Manager window, click
Troubleshoot connection issues
Create Access Connections

Although this connection uses the ODBC driver, it is easier and faster to connect using this method. See "Troubleshoot Access Issues" (page 71) for more information about troubleshooting connection issues. Notes:
l
The Toad Sample Database and established connection that comes pre-loaded in Toad for Data Analysts is an Access database. The connection information for this database is: Database file = C:\Program Files\Quest Software\ToadInstallDirectory\Plugins\Odbc\Sample Database\Quest_Stage.mdb Additional sample files for this database are available in the Project Manager.
To create an Access connection 1. Click on the toolbar (ALT+F+N).
2. Select Access from the Group list box. 3. Review the following for additional information: Database file MDW file Password Select the database to use when connecting. Select the MDW file that is linked to the database. 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 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
55
Click here to view a video of this feature. 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. Click here to view a video about creating connections in Toad for Data Analysts
Create Business Objects Connections

Using Quest Data Services connectivity, Toad provides the ability to connect directly to Business Objects. Note: This feature is only available in the Toad for Data Analysts Premium Edition. To create a Business Objects connection 1. Click on the Connections toolbar (ALT+F+N).
2. Select Quest Data Services from the Group list. 3. Select Business Objects from the Connection Type list. 4. Enter the connection information in the Create New Connection dialog. Review the following for additional information: 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" (page 56) for more information. Note: The URL should be in the following format: http://<server>:<port>/dswsbobje/gaawsservices 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 Select an existing category or create a new one.
56
Note: In Quest Data Services connections, Toad automatically saves the password in the connections.xml file as obfuscated text and in Toad. To add additional password security, use Toad's Master Password feature. 5. Click Connect to save the connection and immediately connect to Business Objects. Note: Click Save to save the connection without connecting. 6. Immediately upon creating an initial new connection, Toad analyzes the queries available and maps them to Toad. When this process is finished (the process may run a few minutes or more), the Table Object Mapping dialog displays. Select the tables to map for this connection. 7. If a query has a parameter, you must enter the default value for the parameter. 8. Click Execute. Notes:
l
In the Table Object Mapping dialog, you can modify the Mapped Name of a table. This is the name that Toad will display in Object Explorer for this table. After creating the connection, you can click in the Object Explorer toolbar to add or remove tables from the connection's table map.
Important Information about Business Objects Connections To create a Business Objects connection in Toad, you must connect to the Query as a Web Service component in Business Objects. The connection URL should have the format: http://<server>:<port>/dswsbobje/gaawsservices 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/gaawsservices. For more information about the Business Objects component, Query as a Web Service, see the documentation at http://help.sap.com/businessobject/product_guides/xir2PP/en/qaaws.pdf.
57
Considerations with Business Objects Connections Consideration Tables vs Business Objects queries Table representation in Query Builder Description What you see represented in Toad as tables are actually Business Objects queries. The representative tables you see in Query Builder do have exposed keys. You can join tables, but you must create the relationship in the Query Builder diagram pane. There is a maximum character limit of 255.
Max character limit Tips:

l
Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help |About. You can specify a proxy server to use for Quest Data Services connections at Tools | Options | Database |Quest Data Services. Business Objects connections are read-only.
Create Excel Connections

Connecting to an Excel file is easy. To create the connection, simply open the Excel file from the Create New Connection dialog . To create an Excel connection 1. Click on the Navigation or Connection Manager toolbar.
2. Select Excel from the Group list. 3. Browse to and select the Excel File name. 4. Complete the Create New Connection dialog. Review the following for additional information: General Tab Category Description Select a category if you want to color code your connection. Tip: The color is applied in the Connection Manager and other connection dialogs. You can also create a new category for your connection. Advanced Tab Description
58
Enable import mode Show system tables Automatically create ranges
Select this checkbox to set IMEX=1 in the connection string, which converts intermixed data to text. Select to display worksheets as system tables. Toad uses the worksheet name suffixed with a dollar sign ($). Select this option if you want Toad to automatically create named ranges. Toad creates one named range in each worksheet (unless the Toad name, AutoRange_<worksheet name>, already exists). Note: Toad does not overwrite the user defined named ranges. The Toad-created named ranges and the user defined named ranges are both visible in the Object Explorer after connecting. Deselect this option if the Excel file contains user defined named ranges and you do not want Toad to create additional named ranges. Important: If you deselect this option, and your Excel file does not contain named ranges, Toad is unable to create tables from your data. The feature is selected by default.
Hide named ranges
Select the named ranges to hide. Note: Named ranges are not displayed until after a connection is created (in the Connections or Connection Properties dialog). In Excel 2007 files, named ranges are not displayed for active connections. Click to open the selected file in Excel. This is useful if you want to modify your file or define named ranges before connecting.
Open in Excel
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. Understand how Toad creates data tables from an Excel file Toad uses Excel named ranges (regions) to define the data to include in a table. Therefore, any data that you want to display and easily query in Toad must be included in an Excel named range (region). You can create named ranges using one of the following methods:
l
Preferred method: You can ask Toad to automatically create named ranges when you create the connection to the Excel file. Toad creates one table from each worksheet and includes the contents of every formatted cell.
59
If you do not want to include a worksheet's entire contents in one named range, or if a worksheet contains more than one table, then define the named ranges ahead of time in Excel.
To create a named range in Excel 1. In the Excel file, select the data that you want to include in the table (including column headings). Then define a named range. In Excel 2003, select Insert | Name | Define. In Excel 2007, right-click the data and select Name a Range.
2. Save your Excel file. In Toad, create a new connection to the file. In the New Connection dialog, deselect Automatically create ranges. To allow Toad to automatically create named ranges When creating a new connection to the Excel file, in the New Connection dialog, select Automatically create ranges. Toad creates one named range for each worksheet and includes the contents of every formatted cell.
Tip: For an Excel file with an existing connection, in the Navigation Manger, right-click the file and select Properties. On the Advanced tab, select Automatically create ranges. Toad creates the named ranges the next time you reconnect to this file. To hide named ranges You can hide an Excel file's named ranges so that they do not display as tables in the Object Explorer. 1. In the Navigation Manager, right-click an Excel file connection and select Properties. Note: In Excel 2007 files, the connection must be inactive for the named ranges to display. 2. On the Advanced tab, select the named ranges to hide. To view or modify connection properties To view an Excel connection's properties, do one of the following:
l
Right-click an Excel file connection in the Navigation or Connection Manager and select Properties. 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.
Click here to view a video about creating connections in Toad for Data Analysts Tip:Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help |About.
60
See "Troubleshoot Excel Issues" (page 71) for more information about troubleshooting Excel connection issues.
Create MySQL Connections

You can create a new connection, or connect to an existing connection from the Create New Connection window. See "Troubleshoot MySQL Issues" (page 82) for more information about troubleshooting connection issues. Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions. To create a MySQL connection 1. Click on the toolbar (ALT+F+N).
2. Select MySQL from the Group list box. 3. Review the following for additional information: Login Tab Connection type Host Description Select the protocol to use when connecting.
Enter the name of the host computer where the database is installed. 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.
Password
Connection timeout SSL
Enter the number of seconds to wait when connecting before the application times out. The default is 15 seconds. If you selected SSL as the connection type, review the following for additional information:
l
Private keybrowse to the location of the SSL key file to use when connecting. CA certbrowse to the location of the trusted certificate authority to use when connecting. Certbrowse to the location of the SSL certificate file to use when connecting.
61
Compress
Select this checkbox to compress the value of any strings and return binary values. Select this checkbox to use an embedded MySQL library instead of the MySQL .NET provider. Note: If you select this option, you must specify libMySQL.dll in the path. 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. Description
Use MySQL libraries
Category
Advanced Tab ODBC driver
Select an ODBC driver to use when executing cross-connection queries using this connection. Tip:You can specify the ODBC driver to use for all connections for this database provider in Tools |Options |Database | MySQL.
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. Click here to view a video about creating connections in Toad for Data Analysts
Create ODBC Connections

The purpose of the ODBC provider is to offer basic connection and querying capabilities to any database that supports an ODBC 3.0 or later driver. For a list of databases tested with the ODBC provider, see the Release Notes. This form of connectivity allows connections to databases such as Netezza, IBM iSeries, Ingres, and Vertica. Because this form of connectivity is generic, it is not full-featured and may not be as robust as the fully exploited providers for databases that use a native provider. To create an ODBC connection 1. Click on the toolbar (ALT+F+N+O).
2. Select ODBC from the Group list box.
62
3. Click 4. Click Add.
in the Data Source Name field.
5. Select an ODBC driver from the list, and click Finish. Note: If creating an Oracle ODBC connection, select the ODBC driver provided by Oracle. The Microsoft ODBC for Oracle driver has less functionality than the driver provided by Oracle. 6. Specify the configuration properties required for the database in the windows configuration dialog. 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. 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. See "Troubleshoot MySQL Issues" (page 82) for more information.
7. Specify the connection properties in the Create New Connection dialog. Review the following for additional information: Use data source name Data source name User Password Select to display the Data source names. Deselect to display the driver names. Select the driver or data source name you added in the previous steps. Enter the user name to use when connecting. 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. Database Specify the location of the database schema. Click to create a temporary connection and display available schemas in the dropdown list.
Information Data Source Name Driver Category Displays the selected driver or data source name.
Displays the ODBC driver associated with the data source. Select or create a category if you want to color code Editor tabs
63
Click here to view a video of this feature. 8. 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. Click here to view a video about creating connections in Toad for Data Analysts
Create Salesforce.com Connections

Using Quest Data Services connectivity, Toad provides the ability to connect directly to Salesforce.com. Note: This feature is only available in the Toad for Data Analysts Premium Edition. To create a Salesforce.com connection 1. Click on the Connections toolbar (ALT+F+N).
2. Select Quest Data Services from the Group list. 3. Select Salesforce from the Connection Type list. 4. Enter the connection information in the Create New Connection dialog. Review the following for additional information: URI Enter the Salesforce.com URL to which you want to connect. Note: An example is https://login.salesforce.com. Username Enter your email login. Note: You must have an email login to connect to Salesforce.com from Toad. Toad does not support single sign-on for Salesforce.com at this time. 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. Security token Enter your Security Token provided by Salesforce. Note: You must have a Salesforce security token to create a Salesforce.com connection from Toad. See "Important Notes about Salesforce.com Connections" (page 64) for more information.
64
Category
Select an existing category or create a new one.
Note: In Quest Data Services connections, Toad automatically saves the password in the connections.xml file as obfuscated text and in Toad. To add additional password security, use Toad's Master Password feature. 5. Click Connect to save the connection and immediately connect to Salesforce.com. Note: Click Save to save the connection without connecting. 6. Immediately upon creating an initial new connection, Toad analyzes the tables available and maps them to Toad. When this process is finished (the process may run a few minutes or more), the Table Object Mapping dialog displays. Select the tables to map for this connection and click Execute. Notes:
l
In the Table Object Mapping dialog, you can modify the Mapped Name of a table. This is the name that Toad will display in Object Explorer for this table. After creating the connection, you can click in the Object Explorer toolbar to add or remove tables from the connection's table map.
Important Notes about Salesforce.com Connections

l l
A Security Token is required to log on to Salesforce from Toad. For information on how to generate a new security token, see the Salesforce documentation at https://login.salesforce.com/help/doc/en/user_security_token.htm.
Considerations and Limitations with Salesforce.com Connections

l l
Toad does not show the native table relationships for Salesforce tables at this time. There is a maximum character limit of 255.
Tips:
l
Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help |About. You can specify a proxy server to use for Quest Data Services connections at Tools | Options | Database |Quest Data Services. Salesforce.com connections are read-only.
Create SQL Server and SQLAzure Connections

You can create a new connection, or connect to an existing connection from the Create New Connection window. See "Troubleshoot SQL Server Issues" (page 85) for more information about troubleshooting connection issues.
65
Click here to view a video about creating connections in Toad for Data Analysts Note:For SQLAzure connections:
l l
You must be given explicit read-access to the master database. You can login to Windows Azure Platform by selecting Tools | Cloud Computing | SQL Azure Portal and providing your credentials. Make sure that no Azure firewall rule restricts your IP address from having access to Azure server. See "Create and Alter Azure Firewall Rules" in the online help for more information.
To create a new connection 1. Click on the toolbar (ALT+F+N).
2. Select SQL Server from the Group list box. 3. Review the following for additional information: Login Tab Server name Description Enter the name of the server to use when connecting. Click to display any servers running SQL Server that are currently active on the network. Notes:
l
For SQLAzure connections, enter InstanceName.database.windows.net in this field. For named instances, enter the MachineName\InstanceName in this field.
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
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. Description
Advanced Tab OBDC driver
Select an ODBC driver to use for this connection when creating
66
cross-connection queries. Tip:You can specify the ODBC driver to use for all connections for this database provider in Tools |Options |Database | SQLServer. 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. To connect to server via Central Management Server Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions. 1. Connect to the server, where the CMS is registered. 2. Right-click a connection and select Connect to Central Management Server. 3. Expand CMS Connections list. 4. Double-click the server to connect to it. Notes:
l l
CMS is available on Microsoft SQL Server 2008 only. User should have an appropriate login (Windows Authentication and grant to connect to selected server are required) created on the server to which he connects via CMS.
67
Create Sybase Connections

You can create a new Sybase IQ, Sybase SQL Anywhere, or Sybase ASE connection, or connect to an existing connection from the Create New Connection window. See "Troubleshoot Sybase Issues" (page 86) for more information about troubleshooting connection issues. Click here to view a video about creating connections in Toad for Data Analysts Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions. To create a Sybase connection 1. Click on the toolbar (ALT+F+N).
2. Select a connection type from the Group list box. 3. Enter the login information. Review the following for additional information: Login Tab Host Description Enter the host name for the connection. Note: This field is only available when you select a Sybase IQ or Sybase SQL Anywhere connection. 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. CharSet Enter the client character set such as UTF-8 in this field if it differs from the default character set. This helps you avoid connection issues. Notes:
l l
This field is not case sensitive. This field is only available when you select a Sybase ASE 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. Description
Advanced
68
Tab ODBC driver Select an ODBC driver to use for this connection when creating cross-connection queries. Tip:You can specify the ODBC driver to use for all connections for this database provider in Tools |Options |Database | Oracle. 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.
Create Teradata Connections

Toad allows you to create a full-featured, native Teradata connection. This type of connection provides complete Query Builder, Query Editor, and Database Explorer functionality. Notes:
l
You must have a Teradata .NET Data Provider installed before you can create a Teradata connection. To use a Teradata connection in a cross-connection query, you must have a Teradata ODBC driver installed. In the Base edition of Toad for Data Analysts, to use a Teradata connection in a crossconnection query, you must use a Teradata ODBC connection instead of a native connection.
To install the Teradata data provider Download and install the Teradata .NET Data Provider from the Teradata Web site.
To create a Teradata connection 1. Click on the Connections toolbar (ALT+F+N).
2. Select Teradata from the Group list. 3. Enter the connection information in the Create New Connection dialog. Review the following for additional information: Login Server name Enter the name of the server hosting the database to which
69
you want to connect. Use Single Sign On Password Select if the user is using a single sign-on authentication system. 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. (Optional) Enter a default Teradata database for the connection. Select an existing category or create a new one.
Default database Category Advanced Mechanism Parameter
(Optional) Select an authentication mechanism from the list. (Optional) Enter the parameters required by the selected authentication mechanism. See your system administrator for these values. (Optional) Enter a new account string. 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.
Account string Character set
Use data encryption
Select if using data encryption.
4. Click Connect to save the connection and immediately connect to the database. Note: Click Save to save the connection without connecting to the database. Tip:Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help |About. To install a Teradata ODBC driver Download and install a Teradata ODBC driver from the Teradata Web site. For a list of supported Teradata ODBC drivers, please see the Release Notes for your version of Toad for Data Analysts.
70
Notes:
l l
Toad does not support the Teradata multi-statement request. You can specify which Teradata Data Directory views to use, X views or Non-X views, in Tools | Options | Database | Teradata.
Troubleshoot Connections
Troubleshoot Access Issues
Review the following solutions to help troubleshoot Access issues pertaining to missing functionality and object information and other problems in Toad.
Missing Functionality and Object Information

Issue Some queries display in the View tab of the Object Explorer, but do not display in the Query tab. Cause/Solution The Access ODBC driver handles saved queries in the following manner:
l
If the stored query does not contain parameters, it is treated as a view and displays in the View tab. If the stored query contains parameters, it is treated as a stored procedure and displays in the Query tab.
Primary key information is unavailable.
The Microsoft Access ODBC driver does not return primary key information for databases. However, in some cases, Toad can obtain this information through additional methods.
Other Issues
Issue A delay occurs between writing a value to a database via one connection and seeing the updated value via another connection. Cause/Solution This delay is the default when you are writing and reading data between two different Jet connections. The delay occurs even if the two connections reside in the same client process. Solution: Use a single connection when updating data.
Troubleshoot Excel Issues

Review the following to help troubleshoot and solve issues involving Excel files.
Toad for Data Analysts Installation Guide Troubleshoot Connections
72
Excel Connections
Issue Tables are limited to 256 columns and 65536 rows. Column names longer than 64 characters are truncated and the remaining characters display as null. Columns that include text values or special characters as part of a numeric value, as well as entries with straight numeric values, result in one of the value sets displaying as null. Cause/Solution This is a known limitation with Excel worksheets.
This is a known limitation with Excel worksheets.
When you connect to Excel, the driver automatically scans the first eight rows in a column and applies the data type used in a majority of those rows to all rows in the column. Any rows that do not meet the majority data type display as null values. Solution 1: Reformat worksheet column and values as text. 1. Open the worksheet in Excel. 2. Format the column that contains mixed data types as Text. 3. You can now connect to this spreadsheet from Toad without any null values displayed. Solution 2: Create an ODBC connection. You can force the ODBC driver to read all rows as Text to avoid null values; however, this can result in issues if you attempt to insert data. 1. Open the Create New Connection window and select ODBC from the Group list. 2. Complete the fields as described in Create ODBC Connections. 3. Enter "IMEX=1", in quotations, in the ExtraParameters field. 4. Click Connect.
Column names that contain an exclamation point (!) are not supported. Tables cannot be altered.
The exclamation point character has a special meaning in Excel. If a column name contains an exclamation point, it is internally converted to a dollar sign ($) character.
Tables cannot be altered when the Excel connection is ReadOnly. Solution: Deselect Read-Only Connection in the Connection
73
Issue
Cause/Solution Properties dialog.
The Primary Keys and Foreign Keys tabs are blank in the Database Explorer. Indexes cannot be created or dropped. Unable to query Excel files without named ranges (regions).
Excel is a spreadsheet, and does not support primary and foreign keys so these tabs are always blank.
The Excel ODBC driver does not support this functionality.
The worksheet you are querying does not have named ranges (regions) defined. Solution: You can query the worksheet from the Editor by entering a dollar sign ($) followed by a cell range to limit the results similar to the following statement:
Select * from (MyWorksheet$A1:C10)
You can also query the entire worksheet by entering a dollar sign ($) after the worksheet name. However, this may also return the worksheet's empty rows and columns. Attempting to connect to or create a new Excel connection results in No user tables could be found message. The Excel file does not have named ranges (regions) defined. If you click OK to close the message, the new connection is created, but no user tables display in Object Explorer. (System tables are displayed, if you selected to show these.) Solution 1: In the Excel file, create named ranges. Solution 2: Ask Toad to automatically create named ranges. 1. Disconnect from the file. 2. In Navigation Manager, right-click the file and select Properties | Advanced. 3. Select Automatically create ranges. The next time you connect, Toad automatically creates named ranges, which are then displayed as tables. See "Create Excel Connections" (page 57) for more information. Unable to query data using an empty string or null value. The underlying data format cannot differentiate between an empty string and null data, so a query with a search condition that contains an empty string does not match any empty strings in the table. This occurs because the empty string is treated as a null value, and a null value never matches anything, not even another null value.
74
Issue Unable to update or delete rows in a table.
Cause/Solution The Excel ODBC driver does not support this functionality. While it is possible to update values, DELETE statements do not remove a row from a table. Basically, you can only insert data in a table. This error occurs if you have more than one named range (region) in the same worksheet, and the named ranges are not separated by blank rows. Solution 1: You must add blank rows between named ranges. Add as many blank rows as you have new records to insert. Solution 2: Include only one named range in each worksheet.
Attempting to insert data results in Cannot expand named range error.
Opening Excel Files in Toad Document Window

Issue Excel menus do not display when you open Excel files in a Toad document window. Cause/Solution The Toad document window cannot display all Excel menus. Solution: Right-click the Excel toolbar and add the equivalent toolbar for the missing menu or functionality. When two or more instances of Excel are open in Toad document windows, toolbars are active for only one instance. Toad document windows support one Excel instance at a time. Opening more than one Excel file disables the Excel toolbars for the additional files. Solution: Open only one Excel file at a time.
Troubleshoot DB2 LUW Issues

Review the following solutions to help troubleshoot DB2 LUW issues pertaining to Toad installation and database connections.
Installation Issues
The following table describes issues related to installing Toad for DB2. Issue System.IO.FileNotFoundException File or assembly name Cause/Solution You are not a member of the DB2ADMIN or
75
Issue DB2AdminWrapper, or one of its dependencies was not found
Cause/Solution DB2USERS group. To install Toad, you must be a member of either group. Solution: Ensure that you have been added to one of these groups.
Cannot access IBM DB2 native tools after installing Toad for DB2 2.0 with previous install of DB2 client v7. Error: "SQL10007N Message "-1390" could not be retrieved. Reason code: "2"."
Toad is bundled with the IBM DB2 v9 client. IBM does not support direct client migration from v7 to v9, so installing Toad on a system that has an existing v7 client may cause errors. Solution: Upgrade the IBM DB2 v7 client to the v8 client. If you upgrade the client after installing Toad, you do not have to uninstall or reinstall Toad. You installed a commercial version of Toad for DB2 after uninstalling the freeware version. Solution: You must remove run time information for the freeware version of Toad from the .NET system.config file.
Error: "Could not load file or assembly 'IBM.Data.DB2.9.1.0, Version=9.1.0.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208' or one of its dependencies. The system cannot find the file specified."
To remove run time information 1. Exit Toad. 2. Navigate to the following .NET framework directory: C:\WINDOWS\Microsoft.NET\ Framework\v2.0.50727\ CONFIG 3. Create a backup copy of the system.config file. 4. Open the system.config file in Notepad. 5. Locate the <runtime> tag delete everything between the runtime tags (including <runtime> and </runtime>). 6. Save the file. 7. Restart Toad.
76
Connection Issues
Issue ERROR [08001] [IBM] SQL1336N The remote host was not found. SQLSTATE=08001 Cause/Solution You are attempting to connect to a database version that is not supported in Toad. Solution: Review the list of supported databases in the Release Notes or Installation Guide. ERROR [58031] [IBM] SQL1031N The database directory cannot be found on the indicated file system. SQLSTATE=58031 Catalog entries have not been imported or defined for the connection. Solution: See "Configure DB2 Client Connections" (page 39) for more information to determine the best method for cataloging a database. A settings file might be corrupt. Solution: Rename your local settings directory so a new one can be recreated. To rename your local setting directory 1. Exit Toad. 2. Navigate to the following settings directory: C:\Documents and Settings\ UserName\Local Settings\ApplicationData\Quest Software 3. Rename the Toad for DB2 version# folder to "Toad for DB2 OLD". 4. Restart Toad and try to connect. Note: Make sure you can view hidden folders in Windows Explorer.
"The type initializer for 'IBM.Data.DB2.DB2Connection' threw an exception." or "SUCCESS - unable to allocate an environment handle."
77
Other Issues
Issue Unable to capture Container Information in DB2 for LUW Multi-Partition Databases Cause/Solution Certain Toad functions require that the DFT_ MON_BUFPOOL 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.
78
Troubleshoot DB2 z/OS Issues

Review the following solutions to help troubleshoot DB2 z/OS issues in Toad.
Installation Issues
Issue Error: "Could not load file or assembly 'IBM.Data.DB2.9.1.0, Version=9.1.0.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208' or one of its dependencies. The system cannot find the file specified." Cause/Solution You installed a commercial version of Toad for DB2 after uninstalling the freeware version. Solution: You must remove run time information for the freeware version of Toad from the .NET system.config file. To remove run time information 1. Exit Toad. 2. Navigate to the following .NET framework directory: C:\WINDOWS\Microsoft.NET\ Framework\v2.0.50727\ CONFIG 3. Create a backup copy of the system.config file. 4. Open the system.config file in Notepad. 5. Locate the <runtime> tag delete everything between the runtime tags (including <runtime> and </runtime>). 6. Save the file. 7. Restart Toad.
79
Connection Issues
Issue ERROR [08001] [IBM] SQL1336N The remote host was not found. SQLSTATE=08001 Cause/Solution You are attempting to connect to a database version that is not supported in Toad. Solution: Review the list of supported databases in the Release Notes or Installation Guide. ERROR [58031] [IBM] SQL1031N The database directory cannot be found on the indicated file system. SQLSTATE=58031 You do not have any catalog entries defined for the connection. Solution: See "Configure DB2 Client Connections" (page 39) for more information to determine the best method for cataloging a database. You do not have SYSADM privileges for the DB2 for z/OS subsystem. Solution: Ensure that you are granted SELECT permissions on the DB2 catalog tables. When using the Time-Sharing Option (TSO) to connect, the user ID, port number, or IP address entered may be incorrect. Solution: Ensure that you use the following for TSO connections:
l l
ERROR [42501] [IBM][DB2] SQL0551N "UserName" does not have the privilege to perform operation "SELECT" on object "SYSIBM.SYSSTMT". SQLSTATE=42501 ERROR [] [IBM] SQL1460N The environment variable "SOCKS_NS" required for SOCKS server name resolution is not defined or not valid.
DB2 user ID for the DB2 subsystem Port number that DB2 listens on, for remote connections, via the DB2 DDF address space IP address for the z/OS subsystem
80
Issue ERROR [56038] [IBM][DB2] SQL0969N There is no message text corresponding to SQL error "-4700" in the message file on this workstation.' when connecting to compatibility mode database. -orAfter connecting, some objects do not display properly or some functionality does not work as designed.
Cause/Solution In general, Toad does not support a z/OS subsystem running in Compatibility mode. Solution: If possible, switch the subsystem's operating mode to Full Function mode. If this is not possible, Toad now provides a message when you connect to subsystem, informing you of that the subsystem is running in compatibility mode and that some features might not be available.
Missing Functionality or Object Information

Issue Unable to browse databases in DB2 for z/OS 8 or later. Cause/Solution The DB2 installation job DSNTISG defines a set of DB2 procedures that the ODBC driver uses. The installation assigns these procedures (namely, those beginning with SYSIBM.SQL*) to a specific Work Load Manager (WLM) environment, which currently might not exist or be defined properly. Solution: Be sure that you have correctly set up and enabled the WLM environment to which the procedure definitions point. Cannot edit data in compatibility mode. In compatibility mode, the ODBC driver does not return enough information for the CommandBuilder to correctly generate update or insert statements. Solution: No solution exists. However, when you connect to a subsystem running in compatibility mode, Toad now provides a message, informing you of this condition and warning you that some features might not be available.
81
Other Issues
Issue [IBM][CLI Driver][DB2] SQL0104N An unexpected token "/*" was found following "". Expected tokens may include: "FROM INTO". SQLSTATE=42601 Cause/Solution The SQL script that you attempted to execute contains commented text delimited by characters that DB2 for z/OS 8 or earlier does not support. Solution: Set an option in Toad that removes comments automatically from a script before you execute it. To have Toad remove comments automatically from SQL before execution 1. Select Tools | Options | Database | DB2 | General. 2. Select Remove comments from SQL statements prior to execution. Poor performance when browsing DB2 for z/OS objects in Toad. Indexes are populated slowly. User-defined indexes on specific system catalog tables can improve performance when you are browsing DB2 for z/OS objects 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
82
Troubleshoot Informix Issues

Review the following solutions to help troubleshoot Informix issues in Toad. Issue Unable to view all available databases. Cause/Solution The InformixODBC driver does not return information about every available database.
Troubleshoot MySQL Issues

Review the following solutions to help troubleshoot MySQL connection issues pertaining to database connections and missing functionality or object information in Toad.
Connection Issues
Issue "InvalidCastException" error when connecting to MYSQL 4.1.14-nt database Cause/Solution This is a known issue in MySQL. Solution: Review the known issue and download a patch from: http://bugs.mysql.com/bug.php?id=12771 Solution: 1. Exit Toad. 2. Locate the MySQL.xml file in the C:\Documents and Settings\username\Local Settings\ Application Data\Quest Software\ Toad for MySQLversion\ ModuleSettings 3. Rename or delete the MySQL.xml file. 4. Restart Toad.
"System.IO.DirectoryNot FoundException"error occurs each time you attempt to connect after installing Toad into a directory other than the default directory.
83

Issue Views tab in Object Explorer is unavailable when connecting to MySQL using the ODBC driver Cause/Solution You are attempting to connect using the 3.51 ODBC driver. This driver is hard-coded to reply that the database does not support views because it needs to connect to MySQL databases prior to version 5. Solution: Use the native MySQL provider included in Toad. Using a MySQL ODBC connection in a cross-connection query results in an error Attempting to execute a cross-connection query using a MySQL ODBC connection (not a native connection) results in the following error: "The table <table name> can not be mapped." Solution: To use a MySQL ODBC connection in a crossconnection query, you must specify a database for the connection. To specify a database for an existing MySQL ODBC connection 1. In the Connection/Navigation Manager, right-click the existing MySQL ODBC connection and select Properties. 2. Click beside the Data source name drop-down list. The ODBC Data Source Administrator dialog opens. 3. On the User DSN tab, select (highlight) the connection's MySQL ODBC driver and then click Configure. The MySQL ODBC Configuration dialog displays. 4. Select a database from the Database list. Notes:
l
Specifying a database using the Connection Properties Database field does not result in a solution. You must follow the procedure above. You can repeat this procedure at any time to specify a different database.
84
Troubleshoot Oracle Issues

Review the following solutions to help troubleshoot Oracle connection issues pertaining to database connections and missing functionality and object information in Toad.
Connection Issues
Review the following to help troubleshoot Oracle: Issue Attempting to connect when Oracle Instant Client is installed results in a System.NullReferenceException error Cause/Solution Solution: In order to connect using the Oracle Instant Client, the directory for 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 for Data Analysts. 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. Unable to select a 64-bit Oracle client from the Current home field in the Oracle Client tab Toad runs as a 32-bit application, even when installed on a 64-bit O/S. Because it is a 32-bit application, Toad is not compatible with 64-bit Oracle clients. Toad does not support Oracle Rdb at this time.
An error occurs when attempting to connect to Oracle Rdb using an ODBC driver.
Missing Functionality and Object Information

Issue Some schemas are not available from the Schema drop-down list in the Object Explorer. Unable to view table data on the Data tab; SQLFetch generates an access violation. Cause/Solution The Oracle ODBC driver cannot display schemas that do not have any tables.
The Oracle ODBC driver is accessing unallocated memory. Solution: Update the Oracle ODBC driver:
l l
For 9i drivers, update to 9.2.0.7.0 or later. For 10g drivers, update to 10.1.0.3.0 or later.
85
Troubleshoot SQL Server Issues

Review the following solutions to help troubleshoot SQL Server connection issues in Toad. Issue Cannot specify a port number when connecting Cause/Solution 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 SQLServer 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 C:\Program Files\Quest Software \Toad for SQL Server\Template\Scripts\ InitialSqlServer.Sql" error message when 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
86
Issue connecting
Cause/Solution 1. Open the SQL Server options page under Tools | Options | Database | SQL Server. 2. Specify the location for the new install's InitialSqlServer.Sql file in the Run Script on new connection field. By default, this file is located in the following directory: C:\Program Files\Quest Software\Toad for Data Analysts version \Templates\Scripts Note: Clicking may result in a "Path not found error". If you receive this error, manually enter the location in the field.
Cannot establish Named Pipes connection
If you are trying to connect to the server using Named Pipes, "Poll service status in connection list" option should be cleared. Solution: 1. Open the options page under Tools | Options | Database | General. 2. Clear Poll service status in connection list checkbox.
Cannot establish Azure connection
Failing to establish Azure connection may indicate that your IP address is restricted from having access to the Azure server. Solutions: 1. Select Tools | Cloud Computing | SQL Azure Portal to login to Azure Portal. 2. Create a firewall rule on the master database, enabling access to current IP address or range. See "Create and Alter Azure Firewall Rules" in the online help for more information.
Troubleshoot Sybase Issues

Review the following solutions to help troubleshoot Sybase issues pertaining to the following in Toad:
87
Connection Issues
Issue Unable to connect to the database. The following message displays: "The ODBCMDA procedures have not been installed on this database..." Cause/Solution Stored procedures that the ODBC driver requires currently do not exist on the server. Solution: Install the required procedures.

Issue Unable to view or export data for objects with non-standard names. Cause/Solution Sybase ODBC driver has issues handling nonstandard names for objects. Solution: When setting up a Sybase connection in Toad, select Use quoted identifiers on the Connection tab in the Adaptive Server Enterprise window to enable the use of quotations in identifiers. Unable to view linked tables. Linked tables store DSN connection information. Solution: Set up the DSN connection information exactly the same on all machines that access the database.
Other Issues
Issue DBMS name showing as SQL Server. Cause/Solution Older versions of the Sybase ODBC driver return SQL Server as the DBMS name. Solution: Upgrade to the latest version of the Sybase ODBC driver, which correctly returns Adaptive Server Enterprise as the DBMS name.
Configure Version Control

About Version Control
Toad integrates with your existing version control system so you can maintain multiple revisions of files. Important: See "Troubleshoot Version Control" (page 95) for more information about issues when upgrading version control from a previous version.
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 Visual SourceSafe (VSS) Concurrent Versions System (CVS) Subversion Server Version Tested VSS 6.0d Client Version Tested VSS 6.0d See "Configure TFS or VSS" (page 89) for more information. CVS 1.11.22 on Solaris CVSNT 2.5.03 on Windows Subversion 1.5.6 on Windows Note:Toad only supports Subversion 1.5.6 or later. CVSNT 2.5.03 See "Configure CVS " (page 91) for more information.
CollabNet Subversion Command-Line Client 1.5.6 Notes:

l
Toad only supports Subversion 1.5.6 or later. Any Subversion client must have svn.exe in its installation directory to use version control in Toad. Tortoise SVN is no longer supported in Toad because it no longer includes svn.exe in its installation directory.
See "Configure Subversion" (page 93) for more information.
Toad for Data Analysts Installation Guide Configure Version Control
89
Supported Provider Team Foundation Server (TFS)
Server Version Tested TFS 2005, 2008
Client Version Tested Visual Studio (2005, 2008) Team Explorer Client See "Configure TFS or VSS" (page 89) for more information.
Note: Toad connects to your version control system based on login information included in the configuration. Your version control client does not need to run for Toad to connect.
Configure TFS or VSS

You can configure version control to work with SQLscripts in the Editor. See "Troubleshoot Version Control" (page 95) for more information. To configure TFSor VSS to work with SQLscripts in the Editor 1. Ensure that a supported version control client is installed on the computer where Toad is installed. See "About Version Control" (page 88) for more information about tested version control clients and supported versions. 2. Open an Editor window. 3. Right-click anywhere in the toolbar area and select Version Control to display the Version Control toolbar. Tip:You can also access version control functionality from the File |Version Control menu when the Editor window has focus. 4. Click to open the Version Control wizard.
5. Review the following for additional information: Version Control System Page Type Description
Select either Team Foundation Server or Visual SourceSafe. Note: If you select TFS, you must specify the workspace name for the provider in the Team Foundation Server Properties window that displays.
Properties
(TFS only) Click this button (beside the Type field) and specify the workspace name for the provider in the Team Foundation Server Properties window.
90
Server
Select one of the following:

l
For TFS, specify the server where your version control provider is installed and the port number (default is 8080) to use in the following format: http://MyServer:Port For VSS, select the folder where the Source Safe client is installed and the srcsafe.ini file (for example: C:\SourceSafe\VSS\srcsafe.ini).
User name/ Password
Enter login information for the version control provider and click Login. Note: For TFS only, if you leave the user name and password fields blank, Toad uses your default Windows credentials. Description
Version Control Settings Page Version control folder
Select the folder on the version control server where you want to check the scripts in. If you already have the Editor-managed scripts under version control, select the folder on the server where these scripts are located. Notes:
l
Version control automatically checks out the scripts in this folder and any subfolders to the location you specify in the Working folder field.
Working folder
Select the root repository folder on the client computer to use as the default working folder for checking SQLscripts out. If you already have Editor-managed SQLscripts under version control, select the existing working folder for these.
6. Tips:
l
See "Add Scripts Using the Editor" in the Toad help for more information.
You can view revision history and revision comments for a script from the History tab; and can also right-click a revision to send it to the Diff Viewer to compare differences.
91
You can enable, disable, or delete a version control configuration under Tools | Options | Version Control |General. You can modify current settings, including whether to require comments when checking objects and scripts in or out, avoid checking scripts in automatically when executing a script in the Editor, disable or delete a version control configuration, etc., from Tools | Options | Version Control |<options page>.
Configure CVS
You can configure version control to work with SQLscripts in the Editor. See "Troubleshoot Version Control" (page 95) for more information. To configure CVS to work with SQLscripts in the Editor 1. Ensure that a supported version control client is installed on the computer where Toad is installed. See "About Version Control" (page 88) for more information about tested version control clients and supported versions. 2. Open an Editor window. 3. Right-click anywhere in the toolbar area and select Version Control to display the Version Control toolbar. Tip:You can also access version control functionality from the File |Version Control menu when the Editor window has focus. 4. Click to open the Version Control wizard.
5. Review the following for additional information: Version Control System Page Type Properties Description
Select CVS. Click this button (beside the Type field) and complete the following in the Command Based Version Control Properties window:
l
BinaryPathEnter the path where the CVS client is installed. For example, if you installed CVSNT, you would enter: C:\Program Files\CVSNT BranchRevisionLeave this field blank if you are working from the trunk in version control. If you are
92
working from a branch, enter the branch number or name in this field. Caution: Specifying HEAD for the BranchRevision parameter can cause errors. Leave the parameter blank when working with the HEAD revision. Server Select the existing working folder for the version control repository or specify the server string. For example, if you are connecting using pserver, you should specify the server string as follows: :pserver:MyServer:Port:/MyWorkingRepository User name/ password Default Version Control Settings Page Version control folder Enter your CVScommand-line user name and password and click Login. Note:The User name field is optional. Description
l
Working folder
6. Tips:
l
See "Add Scripts Using the Editor" in the online help for more information.
93
Configure Subversion
You can configure version control to work with SQLscripts in the Editor. See "Troubleshoot Version Control" (page 95) for more information. To configure Subversion to work with SQLscripts in the Editor 1. Ensure that a supported version control client is installed on the computer where Toad is installed. See "About Version Control" (page 88) for more information about tested version control clients and supported versions. 2. Open an Editor window. 3. Right-click anywhere in the toolbar area and select Version Control to display the Version Control toolbar. Tip:You can also access version control functionality from the File |Version Control menu when the Editor window has focus. 4. Click to open the Version Control wizard.
5. Review the following for additional information: Version Control System Page Type Properties Description
Select Subversion. Click this button (beside the Type field) and complete the following in the Command Based Version Control Properties window:
94
BinaryPathEnter the path where the Subversion client that contains svn.exe is installed. For example, if you installed the CollabNet Subversion Client, you would enter: C:\Program Files\CollabNet Subversion Client Note: Do not include svn.exe in the path. BranchRevisionLeave this field blank if you are working from the trunk in version control. If you are working from a branch, enter the branch number or name in this field. Important: Specifying HEAD for the BranchRevision parameter can cause errors. Leave the parameter blank when working with the HEAD revision.
Server
Select the existing working folder for the version control repository or specify the server string (for example: svn://MyServer). Enter your Subversion command-line user name and password and click Login.
User name/ Password Default Version Control Settings Page Version control folder
Description
l
Working folder
6. See "Add Scripts Using the Editor" in the Toad help for more information.
95
Tips:
l
Troubleshoot Version Control

Troubleshoot Upgrades
For this release, the back-end of version control has been rewritten. If you previously used version control in Toad, the following may occur:
l
If you migrate settings when upgrading Toad, you may have to reconfigure the repository setting in version control if a "Failed to open the settings for module VersionControl reverting to defaults" error displays. To reconfigure the repository, select Tools |Options |Version Control |Defaults and select the previous repository in the Version control folder field. Your previous project settings are applied. In previous releases, the method Toad used to generate the script was different than the current method. After upgrading Toad, a message may display stating that files in version control are different than the local version. If your local version is current, you should check the files into version control.
Troubleshoot Other Issues

Review the following to help troubleshoot issues with version control:
96
VSSIssues Language support
Description VSS 6.0 uses ANSI strings. Consequently, the English-encoded VSS server and client do not handle certain characters in other languages. This issue may also exist on previous or later VSS language installations. VSS is not case-sensitive. Using version control on objects whose names differ by case only can cause history and version-tracking issues. Description If a message stating that, The system cannot find the file specified displays, this usually means that the CVS executable cannot be found in the path you specified in the BinaryPath field of the Command Based Version Control Properties window. Verify that cvs.exe exists in the directory you specified in this field When executing CVS commands, user input is not allowed. This presents an issue when the user is using CVS 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.
Case insensitive CVS Issues System cannot find file
Command execution
Subversion Issues System cannot find file
Description
If a message stating that, The system cannot find the file specified displays, this usually means that the Subversion executable cannot be found in the path you specified in the BinaryPath field of the Command Based Version Control Properties window. Verify that svn.exe exists in the directory you specified in this field When executing Subversion commands, user input is not allowed. This presents an issue 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.
Command execution
Appendix: Contact Quest

Contact Quest Support
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to SupportLink, our self-service portal. Visit SupportLink at http://support.quest.com. From SupportLink, you can do the following:
l l l
Retrieve thousands of solutions from our online Knowledgebase Download the latest releases and service packs Create, update and review Support cases
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies and procedures. The guide is available at: http://support.quest.com.
Toad Community
Get the latest product information, find helpful resources, and join a discussion with the Toad for Data Analysts team and other community members. Join the Toad for Data Analysts community at http://tda.inside.quest.com/index.jspa.
Contact Quest Software

Email [email protected] Quest Software, Inc. World Headquarters Mail 5 Polaris Way Aliso Viejo, CA 92656 USA Web site www.quest.com
See our web site for regional and international office information.
Toad for Data Analysts Installation Guide Contact Quest Support
98
About Quest Software

Quest Software simplifies and reduces the cost of managing IT for more than 100,000 customers worldwide. Our innovative solutions make solving the toughest IT management problems easier, enabling customers to save time and money across physical, virtual and cloud environments. For more information about Quest go to www.quest.com.
DB2 LDAP support
49 33 32 85 71 82 84 86 74 78 85 32 97 17
Index
A Access
Oracle LDAP support share for all session windows troubleshoot Access
create connections troubleshoot application virtualization B
54 Informix 71 Oracle 12 Sybase ASE troubleshoot DB2 LUW
Business Objects troubleshoot DB2 z/OS create connections C understand Citrix contact support install requirements client requirements configure Toad connections D configure DB2 client create Access create DB2 create Excel create MySQL create ODBC create Oracle create SQL Azure create SQL Server create Sybase ASE create Sybase IQ create Sybase SQL Anywhere 39 DB2 54 create connections 50 troubleshoot LUW issues 57 troubleshoot z/OS issues 60 desktop virtualization 61 E 34 Excel 64 create connections 64 ranges 67 troubleshoot 67 67 71 57 57 12 78 74 50 24 corporate deployment 12 customize 7 Toad 28 CVS, configure 91 28 55 troubleshoot SQL Server
Toad for Data Analysts Installation Guide Index
100
I Informix, troubleshoot install Citrix Citrix support client requirements read-only silent L LDAP DB2 support Oracle support license keys look and feel configuration M mst file MySQL create connections troubleshoot O ODBC create connections Oracle Business Intelligence create connections create OBIEE connections troubleshoot R read-only installation 16 37 34 37 84 61 60 82 20 49 33 28 28 82 14 24 12 7 16 17
requirements Citrix client virtualization S Salesforce, create connections server virtualization shortcut keys configure to match other applications silent install create transform file Microsoft installer (MSI) prerequisites SourceSafe, configure SQL Azure create connections SQL Server create connections troubleshoot Subversion, configure Sybase create connections system requirements T Team Foundation Server, configure Teradata create connections TFS, configure 68 89 89 67 7 64 85 93 64 28 17 20 20 18 89 63 12 12 7 12
Toad for Data Analysts Installation Guide Index
101
Toad, customize transform file troubleshoot DB2 LUW connections DB2 z/OS connections Excel Informix issues MySQL Oracle connections SQL Server connections version control tutorials create ODBC connections U uninstall V Version Control configure CVS configure Subversion configure TFS configure VSS troubleshoot virtualization support Visual SourceSafe, configure VSS, configure
28 20
74 78 71 82 82 84 85 95
61
27
88 91 93 89 89 95 12 89 89

Toad For Data Analysts 3.1: Installation Guide

Uploaded by

Copyright:

Available Formats

Toad For Data Analysts 3.1: Installation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Toad For Data Analysts 3.1: Installation Guide

Uploaded by

Copyright:

Available Formats

Toad for Data Analysts 3.

Configure Oracle LDAP Support Create Oracle Connections

Toad for Data Analysts Installation Guide Table of Contents

Create an Oracle Connection

Create Oracle Business Intelligence Connections Configure DB2 Client Connections

Troubleshoot Excel Issues

Troubleshoot DB2 LUW Issues

Toad for Data Analysts Installation Guide Table of Contents

Connection Issues Other Issues

Troubleshoot DB2 z/OS Issues

Troubleshoot Informix Issues Troubleshoot MySQL Issues

Troubleshoot Oracle Issues

Troubleshoot SQL Server Issues Troubleshoot Sybase Issues

Configure Version Control About Version Control

Toad for Data Analysts Installation Guide Table of Contents

Appendix: Contact Quest Contact Quest Support

Contact Quest Software About Quest Software Index

Hard Disk Space

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Specify Application Data Directory Location

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Install Toad Silently

Determine Which Installer to Use

Microsoft Installer file (.msi)

Supports deployment of Toad settings files and license keys.

Toad for Data Analysts Installation Guide Installation

Silent Installation Prerequisites

Silent Installation Using the Executable

Toad for Data Analysts Installation Guide Installation

installation similar to the following command:

Toad for Data Analysts Installation Guide Installation

Silent Installation Using the Microsoft Installer

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

ModuleSettings folder and files

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Install Toad on Citrix Systems

Toad for Data Analysts Installation Guide Installation

Files Migrated During Upgrades

Toad for Data Analysts Installation Guide Installation

Settings.xml SqlServerPlanPrefs.xml ToadSupportBundle.zip Folder Automation (temporary folder) Cache

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Enter the site message included with the license key.

Configure Toad Layouts

Set one of the following:

Toad for Data Analysts Installation Guide Installation

Use this page...

Toad for Data Analysts Installation Guide Installation

Use this page...