Toad for SQL Server 8.1 - Installation Guide

Installation

Install Toad

Note: Your Toad for SQL Server license key determines the edition and will enable Toad for SQL Server functionality accordingly. In many cases, if functionality is disabled within Toad for SQL Server, you may not have an appropriate license to use it. When Toad is running, you can see which components are licensed by selecting Help | About.

To install Toad

1. Run the Installer.

2. Accept the License Agreement.

3. Select the products you want to install and click Install.

Note: Check Prohibit saving passwords during the installation to prohibit users from saving their passwords in Toad.

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.

Use a stand-alone installer to perform a silent install. Obtain your installer files at https://support.quest.com/.

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 Software 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

   You can customize MSIEXEC command-line options and overrides for your installation similar to the following command:

   “ToadInstaller.exe” /S /Lx “C:\temp\installLog.txt” INSTALLDIR=”Drive:\your_install_path” USERNAME=”some_user” COMPANYNAME=”your_company” ALLUSERS=1

   Use the following descriptions to customize the command-line options and overrides for your installation.

   Command-Line Options

   The following MSIEXEC command-line options are used in this example:

   Option	Description
   /L “C:\temp\installLog.txt”	(Optional) Write installation messages to the specified log file. Substitute “C:\temp\installLog.txt” in the example with the fully qualified name of the log file. Enclose this value in double quotations. The installation process creates this file if it does not exist. Otherwise, the existing file is overwritten. You can add additional parameters to the logging option to indicate what type of information to log. /Lx—Adds extra debugging information to the log (used in previous example) /Lv—Specifies verbose output /L*—Log all information, except that specified by x and v /L*v—Log all information, including v (verbose output) /L*x—Log all information, including x (extra debugging info) /L*vx—Log all information, including that specified by v and x See the log section at http://msdn2.microsoft.com/en-us/library/aa367988.aspx for more information about additional logging parameters.
   License="full_path"	Specify the full path to a license file, e.g. License="C:\ProgramData\Quest Software\Toad for SQL Server". Toad for SQL Server to use Toad with the desired license.

   Toad Default Installation Option Overrides

   You can specify the following values to override Toad’s default installation options. Enclose each value in double quotations.

   Option	Description
   INSTALLDIR	(Optional) Specify the absolute path for the directory in which you want to install Toad. If you do not include this path, the installation program defaults to: C:\Program Files (x86)\Quest Software\Toad for SQL Server7.4.
   ALLUSERS	(Optional) Specify one of the following: 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: 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.
   INSTALLSSMS	(Optional) Set the property to "No" not to install Toad plug-in for Microsoft SQL Server Management Studio. Note: If you do not specify this property or specify any other value except "No", Toad plug-in for Microsoft SQL Server Management Studio will be installed.
   ALLOWPASSWORDS=FALSE	(Optional) Set in order to prohibit users from saving their passwords in Toad.
   OPTIONSTEMPLATE	(Optional) Enter a full path to the Options Template that you generated in Tools | Options | General.
   Notes:  All default installation option overrides are case-sensitive. Enclose all values (except for the ALLUSERS value) in double quotations.

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.

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.

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:

   • 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.
   • If you have users with different license requirements (for example, some have Standard licenses and others have Professional licenses), individual licenses should be entered for each user. You should not enter the default license key because it enables all functionality in Toad.