Chat now with support
Chat with Support

Toad Data Point 3.7 - Installation Guide


System Requirements

Review the following client and database server requirements for ToadData Point.

Client Requirements

Before installing Toad, ensure that your client system meets the following minimum hardware and software requirements:


2 GHz Processor (recommended minimum)


2 GB of RAM minimum, 4 GB recommended

Additional RAM Requirements: Using Local Storage, Cross-Connection Query, Business Intelligence connections, or NoSQL connections can require an additional 500 MB of RAM. These features start processes (mysqld.exe, hubproxy.exe) which persist for the Toad session.

Note: The memory required may vary based on the following:

  • 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

800 MB to install Toad

450 MB to run Toad

    Operating System

    Windows Server® 2008 (32-bit or 64-bit)

    Windows Server® 2012

    Windows® 7 (32-bit or 64-bit)

    Windows® 8 (32-bit and 64-bit)

    Windows® 8.1 (32-bit and 64-bit)

    .NET Framework

    The Microsoft® .NET Framework is required. The version is dependent on the operating system.

    .NET 4.5

    Windows Vista SP2, Windows 7, Windows 8, Windows Server 2008 (SP2 or earlier), Windows Server 2008 R2, Windows Server 2012

    .NET 4.0

    Windows XP, Windows Vista (SP1 or earlier), Windows Server 2003


    • This information is provided to aid installation. Toad is not tested on Windows XP. Windows Vista (SP1 or earlier), and Windows Server 2003.
    • The .NET Framework 4 Client Profile is not supported.

    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

    DB2® Client

    Toad no longer installs a DB2 Client along with the Toad application. For full functionality when connecting to a DB2 database, ensure that you have a DB2 Client installed. Toad supports DB2 Client versions 9.7.6 through 10.5.

    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.


    • You cannot use Oracle Direct Connection in a cross-connection 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

    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

    SQL Server® Native Database Provider

    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 Server 2008, Windows 7

    MySQL Native Database Provider

    Windows Server 2008 (32-bit or 64-bit)

    Windows Server 2008 R2 (32-bit or 64-bit)

    Windows 7 (32-bit or 64-bit)

    Windows 8 (32-bit or 64-bit)

    Native Database Server

    Toad supports the following databases:

    Oracle 9i, 10g, 11g, 11g R2, 12c

    Toad has been tested on Oracle Exadata 2.0 running Oracle database 11g R2.

    Limited support of 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

    SQL Server 2012 and SQL Server 2012 Express

    SQL Server 2014 Enterprise and SQL Server 2014 Express


    • SQL Server Compact Edition is not supported.
    • Storage Management is not available on SQL Server Express.

    IBM DB2 for LUW 9.1, 9.5, 9.7, 10.1, 10.5

    IBM DB2 for z/OS 9, 10, 11

    Note: Toad may support IBM DB2 Express and SWE in addition to listed above servers, but note that no testing was performed on it.

    MySQL 4.1, 5.0, 5.1, 5.5, 5.6

    MariaDB 5.5.5 (using MySQL provider)

    SAP ASE 12.5.4, 15.0.2, 15.0.3, 15.5, 15.7, 16

    SAP IQ 15

    SAP SQL Anywhere 12

    Teradata 12.0, 13.0, 13.10, 14, 15

    Access® 2003, 2007, 2010, 2013

    Excel® 2003, 2007, 2010, 2013

    ODBC Database Server

    Toad Data Point 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:

    • DB2 for i5/OS V5R4 and IBM i 6.1
    • Greenplum® Database
    • 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, 7.0
    • PostgreSQL® 8.3.4
    • Vertica 4.1, 5.0, 5.1 (with 4.0, 4.1 ODBC driver), 6.0 (with 6.0 ODBC driver), 6.1, 7.0

    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

    SQL Azure

    Note:  To be able to utilize a majority of Toad functionality, please grant VIEW DEFINITION on the SQL Azure databases you want to work with.

    SQL Server databases running on Amazon EC2

    Toad can manage Amazon RDS and any other cloud or service offering compatible with MySQL.

    Business Intelligence Connections

    Toad has been tested with, and supports, the following Business Intelligence platforms:

    SAP Business Objects XI 3.0, 3.1, 4.1

    Oracle Business Intelligence Enterprise Edition 10g, 11g®

    Microsoft SQL Server Analysis Services

    Google Analytics™

    Azure Data Market



    NoSQL Connections

    Toad has been tested with, and supports, the following NoSQL platforms:

    Azure Table Services

    Apache Cassandra™

    • Note: Toad does not support a CQL API connection (port 9042) to Cassandra at this time. See Known Issues in the Release Notes for more information.

    Amazon DynamoDB

    Apache HBASE™

    Apache Hive™


    Amazon SimpleDB™

    Virtualization Support

    Application Virtualization

    Limited testing has been performed for Citrix® XenApp™ 5.0 on Windows Server 2003 and Citrix XenApp 6.5 on Windows Server 2008 R2.

    See Install Toad on Citrix® Systems for more information.

    Desktop Virtualization (VDI)

    Toad has been tested with vWorkspace™ 7.0 running on Windows XP Professional 32-bit (Service Pack 2).

    Server Virtualization

    Toad has been tested with the following:

    • Oracle VM 3.1 running on Red Hat Enterprise Linux 64-bit with Oracle 11gR2
    • Oracle VM 2.2 running on Windows 2008 32-bit with Oracle 11gR2

    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:

    •  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 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 user—a Power User, Restricted User, Vista standard user—on the computer.

    If a Power User installs Toad, a Restricted User cannot do the following:

    • 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:

    • (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.
    • (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 Vista’s 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:


    • (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:


    • 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.


    Install Toad


    Starting with release 3.2, Toad™ Data Point is available in two editions: Base and Professional.

    To install Toad

    1. Run the ToadInstaller.exe.
    2. Complete the wizard. Review the following for additional information.

    Install Wizard Page Description
    Destination Folder

    Select a destination folder or use the default.

    Install Type

    Typical Install—Select to install Toad normally.

    Read-only Install—Select to install Toad as a read-only application. See Read-Only Installation for more information.


    Specify App Data Directory Location

    Toad Data Point 3.7 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 Data Point (Computer\HKEY_CURRENT_USER\Software\Quest Software\Toad Data Point\3.7), add LOCALSETTINGS with a value of 1.

    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

    Default Location New Location when

    Windows Vista

    Windows Server 2008

    Windows 7

    Windows 8

    C:\Users\username\ AppData\Roaming\Quest Software\Toad Data Point 3.7

    C:\Users\username\ AppData\Local\Quest Software\ Toad Data Point 3.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).

    Self Service Tools
    Knowledge Base
    Notifications & Alerts
    Product Support
    Software Downloads
    Technical Documentation
    User Forums
    Video Tutorials
    RSS Feed
    Contact Us
    Licensing Assistance
    Technical Support
    View All
    Related Documents

    The document was helpful.

    Select Rating

    I easily found the information I needed.

    Select Rating