Toad^Ž for SQL Server

Version 4.6.0

Release Notes

June 03, 2010

Welcome to Toad for SQL Server	New in this Release	Resolved Issues and Enhancements	Known Issues	Third Party Known Issues
System Requirements	Global Operations	Installation	For More Information

Welcome to Toad for SQL Server

Toad for SQL Server is a database development and administration solution that provides productivity features for rapidly creating and executing queries, automating database object management, developing SQL code, as well as instant access to SQL Server expertise.

Developers and administrators have access to a community of users, peers, and experts to help solve development and administration issues and assist in developing applications and feedback for improving Quests products.

Quest Software, Inc., a leading enterprise systems management vendor, delivers innovative products that help organizations get more performance and productivity from their applications, databases, Windows infrastructure and virtual environments.

New in This Release

Review the following sections for updates in this release and new features:

General
Database Administration
Data Management
Query Development

General

You can increase screen real-estate in Toad by pressing SHIFT+ALT+ENTER or selecting View | Full Screen from the menu to hide the default toolbars and display Toad in full screen mode.

In full screen mode, you can switch back to your previous screen size and displayed toolbars by clicking Full Screen beside the menu.

Connections

You can now assign a category such as development or production to connections. This adds an indicator beside the connection in the Connection Manager and color codes Editor tabs. To assign a category to a connection, select an existing category or create a new category from the New Connection or Connection Properties window.

You can select the Show category in explorer and object editors checkbox in Tools | Options | Database | General to apply the color coding to, the Object Explorer window and the navigation pane in Object Editor (Create, Alter, Drop, etc.)windows.

Database Administration

Object Explorer

You can drop, start, or stop traces from the Management node in the Object Explorer. Differences in the icons can help you distinguish between a standard SQL Server trace and a default trace.

In addition to properties for a trace, you can also view events.

Parameters now display for stored procedures and functions in the grid below the selected object in the Object Explorer. For functions, the return value also displays.
A new Storage node has been added under each database for the new Partition Schemes and Partition Functions nodes. For this release, these nodes only allow dropping these objects (although you can create new partition schemes and functions easily from the partitioning wizards). Full-Text Catalogs have also been moved to the Storage node.
You can now right-click a view and select Alter in Editor to make changes in the Editor window instead of the Alter View window.
(SQL Server 2008 only) When altering a table or index, you can now estimate table/partition compression savings on the Storage page.
You can now rename a user from the right-click context menu or the toolbar for users in the Object Explorer.
For SQL Server 2005 and 2008, when creating or altering a login from the Object Explorer, you can now set status options, such as whether the login is enabled, locked, expired, etc.
When creating or altering an index, you can now reorganize selected index columns using arrows.
When editing permissions, you can now multi-select items on the Securables page for removal.
A gray Alerts icon now indicates that an alert is disabled.

ER Diagram

When opening a previously saved Query Builder file, you can right-click the Diagram pane and select Refresh to get the latest objects from the database, including added/removed columns and data type updates.

Data Management

General

For new installs, the default has been set to move the cursor to the previous/next row when the left or right arrow key is pressed. You can set or clear this option in Tools | Options | Environment Grid.

Export Wizard

Support for exporting directly to Excel 2007 and Excel 2010.

Query Development

Query Builder

When opening a previously saved Query Builder file, you can right-click the Diagram pane and select Refresh to get the latest objects from the database, including added/removed columns and data type updates.
An * in the title of the object indicates that the saved version differs from the database version.

When using an IN or NOT IN operator on a DateTime column in a Where condition, you can now select multiple entries or all entries.

Editor

The Rename Tab is back by popular demand. In a previous release, this option was removed because of conflicts with version control, but it has been rewritten to avoid these conflicts. To use this feature, press F2 in an Editor or right-click an Editor tab and select Rename Tab.

The temporary name is now stored as an alias.
Files are now added to the Recent Files list when you drag them into the Editor.
Line numbers now display by default in the Editor window's left margin. You can disable this functionality by clearing the Show line numbers checkbox in Tools | Options | Editor | General.
You can now apply custom format templates to SQL directly from the Editor by selecting a template from the Format drop-down list on the toolbar. You can customize existing templates or create new templates in Tools | Options | Editor | Formatter.

Also, it is now easier to save, share, and delete custom format templates in Tools | Options | Editor | Formatter.

Toad Scripts now include a GROUPBY function that automatically groups the results. This allows you to save grouping preferences as part of the script so you do not have to manually re-group them using the grouping feature in the grid each time you run the script.

Note: Toad Script functions automatically terminate a batch. To avoid terminating before a batch completes, make sure that any Toad Script functions are placed between batches.

Improved Result Set grouping. Although 4.5 merged results from all queries into a single grid, it only did this if all the results matched. Any mismatch or error caused each result set to display in its own grid. Now, like result sets are combined into a single grid and errors do not short circuit this behavior. For example, if you wanted to run a LiteSpeed license check on all instances whether they had LiteSpeed installed or not, you could run exec master.dbo.xp_sqllitespeed_licenseinfo and a single grid containing those connections with results would display.

Group Execute

When saving an Editor file where Group Execute is enabled, Toad defaults to saving the file as a Toad Editor File (.tef). If you save as this file type, the selected group and any filters are also saved in the file.
You can also see how many targets have been selected.

Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release of Toad for SQL Server.

Feature	Resolved Issue	Defect
Installation/ Upgrade	If you migrate settings from the a previous release, attempting to search www.SQLServerPedia.com using SHIFT+F1 in the Editor or using the default Quick Search field (top-right) no longer results in missing functionality.	ST65352
Connections	Currently, Toad does not support restricted SQL Server users. Attempting to connect to a database if you have restricted SQL Server privileges results in an "Unable to cast object of type 'System.DBNull' to 'System.String'" error message.	ST66935
	In some instances, connecting to a database no longer results in a "Data at the root level is invalid" error.	ST67430
	Attempting to connect to a database and immediately view a table's Data tab in the Object Explorer no longer results in an error.	ST66935
	Saved Toad Connection Script (.tcs) files now connect to a database if the connection was automatically imported from Management Studio.	ST55997
Data	When viewing data, all Chinese characters now display correctly.	ST63165
Editor	Opening a very large file in the Editor no longer results in an error.	ST41829
	Code Completion updates: In some instances, code completion generated an error when typing a SELECT statement. This issue has been resolved. After entering "SELECT", pressing SPACE now invokes code completion. By default, a list of tables and views display at the top of the code completion list. If you select an owner or database from the list, Toad inserts that object name. However, if you select the actual table, view, or other object name, Toad inserts the text "FROM objectname". It also leaves the cursor at a space before the "FROM objectname". For example, if you select the table Person.Address in the AdventureWorks database you would end up with the following: SELECT \| FROM Person.AdventureWorks The \| character represents the cursor position. From there, you can press CTRL+PERIOD to invoke code completion again and select a list of columns from the table you just inserted. For Code Completion to work with INSERT statements, you must specify the INTO keyword.	ST60775 ST66798 ST64519
	You can now resize the batch pane in the Execution Plan tab.	ST64432
Import Wizard	You can now import Excel 2007 files that are saved using an xlsx format.	ST42416
Object Explorer/ Database Explorer	When browsing objects, a "System.InvalidOperationException: There is already an open DataReader associated with this Command which must be closed first" error no longer occurs.	ST60516
	If you execute a script in the Editor with autocommit disabled, and then hover over a node in the Object Explorer, Toad no longer appears to hang.	ST55294
	When executing a script in an object editor window (Create/Alter/Drop), the execution now occurs in the background so you can continue to use Toad.	ST66831
	Agent Node: (SQL Server Express Edition only) When selecting an object type under the Agent node, Toad no longer closes unexpectedly.	ST67533
	Databases: Performance has improved when generating a data script for a table that has an IDENTITY column. Copy/Move Databases wizard: When copying a database using the Copy/Move Database wizard, a warning message now displays if the required SQL Server Backwards Compatibility tools are not installed. When copying or moving a database using the Copy/Move Database wizard, if you select the Schedule package execution option on the Select Package Execution page, you can now automatically delete the job if it succeeds. Backup Database window: When backing up with LiteSpeed, you can now set the throttle option under Advanced options on the General page. The SQL Script in the Backup Database window is now formatted to make reading it easier.	ST55477 ST54898 ST41708 ST59877 ST59922
	Tables: You can now disable a table trigger without receiving an error message. (SQL Server 2008 only) You can view row and page compression in the Storage page of the Create/Alter windows for both tables and indexes. Also, when altering a table or index, or selecting Storage \| Manage Compression from the Object Explorer, you can click Estimate at the bottom of the Storage page to estimate the savings if the table or index is partitioned. When checking tables, a confirmation dialog now displays the T-SQL script that will be executed prior to checking the tables. You can now view FileStream information for a table on the Columns tab (right-click a table and select View Details).	ST55940 ST66416 ST61238 ST63202
	Views: Comments now display when viewing object details in the Script tab.	ST66015
	Functions: You can now set extended properties for input parameters.	ST65581
	Linked Servers: Tables and views now display below the Linked Servers node.	ST47176
	Logins: (SQL Server 2008 only) You can view all credentials mapped to the current login in a Mapped Credentials tab (right-click a table and select View Details).	ST65059
	Stored Procedures: When altering a stored procedure, the output parameter is no longer reset to False. When right-clicking a procedure and selecting Alter Stored Procedure in Editor, an error no longer occurs.	ST66660 ST67712
Options	If you restart Toad immediately after assigning or removing a keyboard shortcut, the shortcut setting now persists.	ST49841
Query Builder	When reverse engineering a query from the Query tab or the Editor, the Diagram tab now supports a SELECT statement where the columns are qualified with the database name.	ST49731
Version Control	The Update Database function for version control often requires that objects be dropped and recreated. If tables are referenced by Foreign Key constraints, an error no longer occurs when executing the script.	ST42093
	Updating the file extension to a format other than .sql now persists in Tools \| Options \| Version Control \| Locations.	ST64121
	On Subversion, adding a large number of objects no longer decreases performance.	ST50279

Known Issues

The following is a list of issues known to exist at the time of the Toad for SQL Server release.

Feature	Known Issue	Defect
Installation/ Upgrade/ Uninstall	Customized options selected in the Configuration wizard are not applied if you are running Toad as a Restricted user. Workaround: Customize these settings in the Options pages in Toad (Tools \| Options from the menu)	ST42154
	(Windows Vista and 7 only) If you double-click Toad.exe to install the product, UAC may be disabled during the installation and may not be re-enabled when the installation completes. Workaround: Right-click the Toad.exe and select Run as Administrator to install the product. If you have already installed the product, manually enable UAC after the installation.	ST68492
	(Toad for SQL Server Xpert only) If you install Toad for SQL Server 4.5 and 4.6 side-by-side, and later uninstall Toad for SQL Server 4.5, SQL Optimizer for SQL Server does not uninstall correctly. If you later send a statement in Toad for SQL Server 4.6 from the Editor window to the SQL Optimizer, the Optimizer applies the currently selected database as the object's user name. Workaround: Uninstall Toad for SQL Server 4.6, and then reinstall Toad for SQL Server 4.6. Note that all user settings are preserved when you reinstall Toad.	ST69268
Connections	If you migrate settings from a previous version, the Run script on new connection option in Tools \| Options \| Database \| SQL Server may point to the path from the previous version. If you later delete the Application Data Directory for the previous version, which contains the script, attempting to connect to any database results in a path not found error. You can click OK and continue working. Workaround: Select Tools \| Options \| Database \| SQL Server and navigate to the location of the latest connection script in the Application Data Directory. By default, this script is located in the following directory. Windows 2003 or XP: C:\Documents and Settings\username\Local Settings\Application Data\Quest Software\Toad for SQL Server 4.6\Templates\Scripts\InitialSqlServer.Sql Windows Vista or 7: C:\Users\username\AppData\Roaming\Quest Software\Toad for SQL Server 4.6\Templates\Scripts\InitialSqlServer.Sql	ST68623
General	(Windows Vista and Windows Server 2008 only) In some cases, attempting to open a SQL file from the Open dialog results in an "Object reference not set to an instance of an object" error message. Toad uses the Microsoft Distributed Transaction Coordinator (DTC) to get Full-Text Search status for a file, but DTC is disabled by default on Windows Vista and Windows Server 2008. Workaround: Enable Network DTC Access on the Toad client. See http://technet.microsoft.com/en-us/library/cc753510(WS.10).aspx for more information.	ST65049
Data	For some queries, attempting to right-click a row and selecting Row Count results in a message stating that the row count could not be determined.	N/A
Debugger	Currently, you cannot debug scripts on SQL Server Express databases.	ST65086
Editor	When using the View Object at Cursor (SHIFT+F4) feature, triggers are not found.	ST41627
Editor	Starting with the 4.6 release of Toad, any files that you save as Toad Editor Files (.tef) cannot be opened in a previous version of Toad. Attempting to open a newly saved .tef file in a previous version of Toad results in unreadable data. However, you can open any .tef files created in a previous version of Toad with the Toad for SQL Server 4.6 release, and everything displays properly.	N/A
Export Wizard/One Click Export	Blob and Binary data types, including FileStreams, cannot be exported in this release.	ST41665
Export Wizard/One Click Export	Limitations when exporting fractional seconds: When exporting to an Access Database File, exports do not support fractional seconds, so the additional data is not exported. When exporting to an Excel instance, exports support only 3-digits for fractional seconds. However, if you export to an Excel file, it supports all fractional seconds.	N/A
Import Wizard	Attempting to import data that was exported to an Excel instance where the fractional seconds were truncated results in an error.	N/A
Log Reader	Currently, the Log Reader does not support new SQL Server 2008 data types	ST59571
Log Reader	The Log Reader requires version 8.0 DDL files in the Microsoft Visual C++ 2005 SP1 Redistributable Package. If these files do not exist on the client, you will need to install them to use some functionality in the Log Reader. Workaround: Download and install the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) on the client from: http://www.microsoft.com/downloads/details.aspx?FamilyID=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en	N/A
Object Explorer/ Database Explorer	Databases: Currently, if you select the Enable database backup checking checkbox in Tools \| Options \| Database \| SQL Server, the list of databases in the Object Explorer do not indicate the backup status until you press F5 to refresh the list.	ST63855
	Tables: Currently, you cannot perform an extended alter on a table with a FileStream column. This includes the following actions: Changing the column order of the table Adding a new column in the middle of the table Changing a column attribute like an IDENTITY	ST56029
	Table and Index Partitioning: Currently, you cannot create or manage a partition on a table or index that includes a FileStream column. When changing a partitioned table to a non-partitioned table, the Estimate button is disabled so you cannot estimate the compression savings. Workaround: After you finish altering the table, right-click the table and select Storage \| Manage Compression to estimate the compression savings. Currently, estimating index compression savings runs a full table compression savings query, so the estimation may be slow on large tables.	ST59194 ST67986 ST68131
	Maintenance Plans: (Windows 7 only) Attempting to create a maintenance plan on Windows 7 results in an exception error.	ST68201
Service Broker	Currently, Service Broker does not support SQL Server 2008.	ST60874
SQL Optimizer	For a list of known issues, see the SQL Optimizer release notes.	N/A
Version Control	If you migrate settings from Toad 4.1 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. Workaround: 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.	ST63004
	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 objects or files in version control are different than the local version. If your local version is current, you should check the objects and files into version control.	N/A
	Version control does not support CLR objects.	ST52089

Third Party Known Issues

The following is a list of third party issues known to exist at the time of Toad for SQL Server release.

Feature	Known Issue	Defect
Export Wizard/One Click Export	To export to an Office 2003 or 2007 Excel instance, the Office Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from one of the following locations: 2003 PIAs http://www.microsoft.com/downloads/details.aspx? FamilyID=3c9a983a-ac14-4125-8ba0-d36d67e0f4ad& DisplayLang=en 2007 PIAs http://www.microsoft.com/downloads/details.aspx? familyid=59DAEBAA-BED4-4282-A28C-B864D8BFA513&displaylang=en	N/A

Feature

Known Issue

Defect

Export Wizard/One Click Export

To export to an Office 2003 or 2007 Excel instance, the Office Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from one of the following locations:

2003 PIAs

http://www.microsoft.com/downloads/details.aspx?
FamilyID=3c9a983a-ac14-4125-8ba0-d36d67e0f4ad&
DisplayLang=en

2007 PIAs

http://www.microsoft.com/downloads/details.aspx?
familyid=59DAEBAA-BED4-4282-A28C-B864D8BFA513&displaylang=en

N/A

System Requirements

Client Requirements

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

Platform	600 MHz minimum, 1 GHz recommended
Hard Disk Space	104 MB of disk space is required to run Toad.
Memory	512 MB of RAM minimum, 1 GB recommended 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
Operating System	Windows Server 2003 (32-bit or 64-bit) Windows XP Professional (32-bit or 64-bit) 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) Important: Toad uses the Microsoft Distributed Transaction Coordinator (DTC) when opening a SQL file to get Full-Text Search status, but DTC is disabled by default on Windows Vista and Windows Server 2008. If you are using either operating system, ensure that Network DTC access is enabled on the Toad client. See http://technet.microsoft.com/en-us/library/cc753510(WS.10).aspx for more information about enabling DTC access.
.NET Framework	Microsoft .NET Framework 3.5 (Service Pack 1) Notes: The .NET Framework Client Profile is not supported. To run Toad, the .NET security policy must be set to unrestricted. See User Requirements for more information.
Additional Requirements	Web Browser Microsoft Internet Explorer 6.0 or later PDF Viewer Adobe AcrobatReader 7.0 or later (for viewing the Toad for SQL Server Installation Guide) Maintenance Plans Review the following requirements for using Maintenance Plans: Integration Services that may be a part of the Client Tools 2005/2008 or a part of SQL Server (to take advantage of Integration Services (SSIS) in maintenance plans) (For SQL Server 2008 only) Management Tools - Basic feature from the SQL Server Installer 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. Copy/Move Database Wizard The SQL Server Backward Compatibility package is required to use the Copy/Move Database wizard.

Server Requirements

Before installing Toad for SQL Server, ensure your server meets the following minimum hardware and software requirements:

Operating System	Windows Server 2000 (Service Pack 4 or later) Windows 2000 Professional Edition (Service Pack 4 or later) Windows XP 32-bit (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 and 64-bit Windows Server 2008 32-bit or 64-bit Windows Server 2008 R2 (64-bit) Windows 7 (32-bit or 64-bit)
Database Support	SQL Server 2000 (Service Pack 3 or later), 2005 (Service Pack 2 or later), 2008 Note: SQL Server Compact Edition is not supported.
.NET Framework	Microsoft .NET Framework 3.5 (Service Pack 1)
Additional Requirements	Maintenance Plans To take advantage of Integration Services (SSIS) in maintenance plans, you must install the following: Integration Services that may be a part of the Client Tools 2005/2008 or a part of SQL Server (For SQL Server 2008 only) Management Tools - Basic

Citrix Requirements

Limited testing has been performed for Citrix support on Windows Server 2003 Enterprise Server (Service Pack 2) using the MetaFrame Presentation Server 5.0 and Citrix Presentation Server Clients 10.2. See "Install Toad on Citrix Systems" in the Toad for SQL Server Installation Guide.

User Privilege Requirements

The following user privileges are required for installing and running Toad for SQL Server:

Only Power users and Administrators can install Toad.

If a Power user installs Toad, a Restricted user can run the application but cannot
- Associate file extensions.
- See the Toad shortcut icon on the desktop or the Toad menu option in the Windows Start menu. As a workaround, Restricted users can create a shortcut to the application and place it on their desktop from the install directory.

If an Administrator installs Toad, the Administrator can share the Toad shortcut icon on the desktop and the Toad menu option in the Windows Start menu with any user on the computer.
To run Toad, the .NET security policy must be set to Unrestricted. To modify the security policy:

From the Windows Start menu, select Settings | Control Panel.

Double-click Administrative Tools.

Double-click Microsoft .NET Framework 2.0Configuration.

Click + to expand My Computer,and then select the Runtime Security Policy node. A list of tasks for the node display in the right panel.

Click Evaluate Assembly from the list of tasks in the right panel. An Evaluate an Assembly window displays.

Browse to the location of Toad.exe in the File field.

Click Next to view permissions for Toad.exe.

Set the permission to Unrestricted.

Silent Install Requirements

Before you perform a silent installation, the following software must be installed on every system on which you are installing Toad:

Microsoft .NET Framework 3.5 (Service Pack 1) or later

For information about installing Toad silently, see "Install Toad Silently" in the Installation Guide.

Debugging Requirements

Verify the following general requirements to ensure that the Debugger operates properly for all SQL Server installations:

Disable all firewalls or open corresponding ports. Windows XP (Service Pack 2) includes an embedded Windows firewall that should be disabled or ports opened as well. Specifically, the TCP 135 port must be opened and Toad.exe must be added to the Exceptions list. The same is true for the remote (SQL Server) computer--TCP 135 port must be opened and sqlservr.exe must be added to the Exceptions list.
Stop any antivirus software that can lock the corresponding components, settings, etc.
Check your security policy because it may include an access lock to the remote server.

Note: The security policy can be applied to the domain or local computer.

Note: Currently, you cannot debug SQL/CLR code.

Configure Debugging for SQL Server 2008

To debug locally, perform the following on the Toad client

Install the SQL Server 2008 Client Tools on the Toad client.
If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

To debug remotely, perform the following

Install the SQL Server 2008 Client Tools on the Toad client.
Make sure the following permissions are set:
- Your Windows account that Toad is running under must be a member of sysadmin server role in the SQL Server being debugged.
- Your server login must also be a member of the sysadmin role. This login can be your Windows user account (Windows authentication), or a SQL Server login (SQL Server authentication).
  To create a server login from your Windows account and add it to the sysadmin role, a user who already has sysadmin privileges must execute the following:
  sp_addsrvrolemember 'Domain\Name', 'sysadmin'
  where Domain\Name is your Windows login.
If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

Configure Debugging for SQL Server 2005

To debug locally, perform the following on the Toad client:

Install the SQL Server 2005 Workstation Component option of the SQL Server 2005 installation.
If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

To debug remotely, perform the following:

On the Toad client, do one of the following:
- Install the SQL Server 2005 Workstation Components option of the SQL Server 2005 installation.
- Copy and register the ssdebugps.dll (debugging host component) on both the client and server. This file is located by default in the following directory on the server where SQL Server 2005 is installed:
  C:\Program Files\ Common Files\Microsoft Shared\SQL Debugging
  
  To register this file, open a command prompt and enter the following command: regsvr32 ssdebugps.dll
  
  Note: If you are unable to locate this file, you can run the remote debugging setup component (rdbgsetup.exe). This file is located by default in the following directory on the server where SQL Server 2005 is installed: C:\Program Files\Microsoft SQL Server\90\Shared\1033
Make sure the following permissions are set:
- Your Windows account that Toad is running under must be a member of sysadmin server role in the SQL Server being debugged.
- Your server login must also be a member of the sysadmin role. This login can be your Windows user account (Windows authentication), or a SQL Server login (SQL Server authentication).
  
  To create a Server login from your Windows login and add it to the sysadmin role, a user who already has sysadmin privileges must execute the following:
  
  sp_addsrvrolemember 'Domain\Name', 'sysadmin'
  
  where Domain\Name is your Windows login
  
  Note: By default, Windows administrators on a machine running SQL Server are SQL Server sysadmins on that machine.
If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

Configure Debugging for SQL Server 2000

To debug locally, perform the following on the Toad client:

Make sure that SQL Server 2000 with Service Pack 3 or Service Pack 4 is installed.
If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

To debug remotely, perform the following:

On the Toad client, do one of the following:
- Make sure that SQL Server 2000 with Service Pack 3 or Service Pack 4 is installed.
- Copy and register the sqldbg.dll and sqldbreg2.exe (debugging host components) on both the Toad client and server. These files are located by default in the following directory on the server where SQL Server 2000 is installed:
  
  C:\Program Files\Common Files\Microsoft Shared\SQL Debugging
  
  To register these files, open a command prompt and enter the following commands:
  
  regsvr32 sqldbg.dll
  
  sqldbreg2.exe /RegServer
Note: The Remote Procedure Call (RPC) service should be started on both the Toad client and server.
Make sure the following permissions are set:
- Your Windows account that Toad is running under must be a member of the sysadmin server role for the instance you are debugging.
- Your server login must also be a member of the sysadmin role. This login can be your Windows user account (Windows authentication), or a SQL Server login (SQL Server authentication).
  To create a server login from your Windows account and add it to the sysadmin role, a user who already has sysadmin privileges must execute the following:
  sp_addsrvrolemember 'Domain\Name', 'sysadmin'
  where Domain\Name is your Windows login.
- DCOM Access permissions must be granted for the system account and the group or user who needs access.
  To verify permissions:
  1. Open a command prompt and run dcomcnfg.exe.
  2. Expand Component Services, Computers.
  3. Right-click My Computer and select Properties.
  4. Select the COM Security tab.
  5. Under Access Permissions, click Edit Default, and verify permissions.
Note: By default, Windows administrators on a computer running SQL Server are SQL Server sysadmins on that computer.
If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Far-East Asia, Japan.

This release has the following known capabilities or limitations:

Quest SQL Optimizer for SQL ServerThis release supports any single-byte character set. Double-byte or multi-byte character sets are not supported. In this release, all product components should be configured to use the same or compatible character encoding and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America.

Installation

The Toad for SQL Server release package contains the following products:

Toad for SQL Server version 4.6.0
Product Documentation, including:
- Installation Guide
- Online Help
- Release Notes

Installation Instructions

See the Toad for SQL Server Installation Guide for installation information, including silent installation.

For More Information

Contact Quest Software

info@quest.com

Mail

Quest Software, Inc.

World Headquarters

5 Polaris Way

Aliso Viejo, CA 92656

USA

Web site

www.quest.com

See our web site for regional and international office information.

Contact Quest Support

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.

From SupportLink, you can do the following:

Quickly find thousands of solutions (Knowledgebase articles/documents).
Download patches and upgrades.
Seek help from a Support engineer.
Log and update your case, and check its status.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.

Note: This document is only available in English.

Š 2009 Quest Software, Inc.

This document 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

Web site: www.quest.com

Email: legal@quest.com

Refer to our web site for regional and international office information.

Trademarks

Quest, Quest Software, the Quest Software logo, AccessManager, ActiveRoles, Aelita, Akonix, AppAssure, Benchmark Factory, Big Brother, BusinessInsight, ChangeAuditor, ChangeManager, DeployDirector, DirectoryAnalyzer, DirectoryTroubleshooter, DS Analyzer, DS Expert, ERDisk, Foglight, GPOADmin, Imceda, IntelliProfile, InTrust, Invirtus, iToken, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, LogADmin, MessageStats, Monosphere, NBSpool, NetBase, NetControl, Npulse, NetPro, PassGo, PerformaSure, Quest Central, Quest vToolkit, Quest vWorkSpace, ReportADmin, RestoreADmin, SelfServiceADmin, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Storage Horizon, Tag and Follow, Toad, T.O.A.D., Toad World, vAutomator, vControl, vConverter, vFoglight, vOptimizer Pro, vPackager, vRanger, vRanger Pro, vSpotlight, vStream, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vBackup, Vizioncore vEssentials, Vizioncore vMigrator, Vizioncore vReplicator, Vizioncore vTraffic, Vizioncore vWorkflow, WebDefender, Webthority, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this document are property of their respective owners.

Contents