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, and 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.

All of this comes with the backing of Quest Software, a healthy and growing corporate entity that can provide the necessary training, support, and superior customer service demanded by IT management.

General

Upgrades:

If you migrate settings during an upgrade, Toad only migrates shared reports and project manager files if you are using the default directory in the Network Settings option page (Tools | Options | Environment | Network Share). If you specified a custom network share directory, the files will not be migrated.

Performance Improvements:

Options:

Database Administration

Query Development

Query Builder:

You can determine the connection used by a query by placing the cursor over the Query Builder tab.

Editor:

The Document Recovery feature is now supported when running multiple instances of Toad.

SQL Optimizer:

Data Management

Automation

Resolved Issues and Enhancements

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

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	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).	ST#42154 CR#216699
Startup	(Windows Vista on Toad client only) If you initially start Toad when logged in as a standard user and enter a license key, the license key should be saved to: C:\Program Files\Quest Software\Toad for SQL Server 4.1 However, a standard user does not have write privileges in Vista to C:\Program Files so the key is saved to the following directory instead: C:\Users\username\AppData\Local\VirtualStore\Program Files\Quest Software\Toad for SQL Server 4.1 If you later start Toad as an administrator, you are prompted to enter the key again because it is not in the C:\Program Files directory.	N/A
Connection	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: C:\Documents and Settings\user\Local Settings\Application Data\Quest Software\Toad for SQL Server 4.0\Templates\Scripts\InitialSqlServer.Sql	ST#42899
Data Reports	Currently, you cannot create a Label Report in the Toad Data Report wizard.	ST#42133 CR#215945
Debugger	You cannot debug stored procedures with the following input parameters in this release: Binary Varbinary Bit Timestamp Image	ST#41538 CR#133602 ST#41539 CR#133634 ST#41540 CR#133636
Editor	When using the View Object at Cursor (SHIFT+F4) feature, triggers are not found.	ST#41627 CR#164917
Editor	Settings specified in the Insert/Replace page under Tools \| Options \| Editor \| Formatter are not applied for insert statements.	ST#50363
Export Wizard/ One Click Export	Binary data types cannot be exported in this release.	CR#170430 ST#41655
Export Wizard/ One Click Export	When exporting large results sets (approximately 500K), you may run out of memory before the operation completes. Workaround: Create a view for the query and export using that view.	ST#41935 CR#203483
Import Wizard	Currently, you cannot import Excel 2007 files because they are saved using an xlsx format. Workaround: Save the Excel 2007 file as a 2003 compatible file before importing it.	ST#42416 CR#221667
Object Explorer/ Database Explorer	Currently, a script is not generated when you right-click an object and select Send To \| Editor as Script for the following: Users Roles Schemas Logins	ST#50651
	If you execute a script in the editor with autocommit disabled, and then hover over a node in the Object Explorer, Toad appears to hang because it is waiting for you to either commit or rollback the current transaction. Workaround: Commit or rollback the editor transaction.	ST#55294
	Tables: Attempting to enter data for an XML data type in the Data tab results in an error.	ST#42580
	Databases: When restoring a database, if you add a differential backup file and then add a Full backup file, the restore fails because files are scripted in the order they are added. Workaround: Add the backup files in the correct order before restoring the database. Currently, Toad does not support running SQL Server in 7.0 or lower compatibility mode.	ST#51164 ST#42782 ST#53550
	Stored Procedures: When altering a stored procedure, changes made to the ANSI nulls field or Quoted identifier field are not saved.	ST#44201
	Maintenance Plans: (LiteSpeed 4.8 plans converted to SSIS plans) When adding a Back Up Database task to a LiteSpeed 4.8 Maintenance Plan, selecting the Remove files older than checkbox does not remove the 4.8 Maintenance Plan.	ST#52721
Query Builder	The Diagram tab does not support a SELECT clause where the columns are qualified with the database name. Workaround: When you visualize the query to display in the Diagram tab, Toad automatically creates calculated columns for the columns qualified with a database name. This allows you to execute the query and return the correct result set.	ST#49731
Reports	Currently, the schema report contains information for tables, views, and procedural objects.	ST#48513
SQL Optimizer	For a list of known issues, see the SQL Optimizer release notes.	N/A
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, the following error occurs when executing the script "Could not drop object N because it is referenced by a FOREIGN KEY constraint."	ST#42093 CR#214601
	(TFS only) If you have not selected a sub-project, attempting to add an object results in an error. Workaround: Select Tools \| Options \| Version Control \| Defaults and specify a sub-project in the Version control folder field.	ST#51033
	If you disable a version control configuration in Tools \| Options \| Version Control \| General, and then enable the configuration, when you click OK a null reference error displays. Version control is enabled and you can ignore this error.	ST#51933

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

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

CR#138239

Upgrade and Compatibility

For information about upgrading refer to the Installation Guide available from the Windows Start menu under Program Files | Quest Software | Toad for SQL Server 4.1 | Documentation.

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
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
Hard Disk Space	133 MB of disk space for installation Note: The disk space required may vary based on the edition of Toad selected for installation.
Operating System	Windows^® 2000 Note: The Automation feature requires the .NET Framework 3.0 or later, which is not supported on Windows 2000. Windows Server 2003 Windows XP Professional (32-bit or x64) Windows Vista (32-bit or x64) Windows Server 2008
Additional	.NET Framework Microsoft .NET Framework 2.0 or later Notes: Consider the following: To run Toad, the .NET security policy must be set to unrestricted. For more information, see User Privilege Requirements. To use the Automation feature, the .NET Framework 3.0 or later must be installed. (Optional) Spotlight on SQL Server Spotlight on SQL Server 4.5 or later Web Browser Microsoft Internet Explorer 6.0 or later PDF Viewer Adobe^® Acrobat^® Reader 7.0 or later (for viewing the Toad for SQL Server Installation Guide) Maintenance Plans To take advantage of Integration Services (SSIS) in maintenance plans, you must install Client Tools 2005 on the client where Toad is installed.

Server Requirements

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

Operating System

Windows 2000 Server with SP4 or later

Windows 2000 Professional Edition with SP4 or later

Windows XP (32-bit with SP2 or later; x64)

Windows Server 2003 (32-bit or x64 with SP1 or later)

Windows Vista (32-bit or x64)

Windows Server 2008 (32-bit or x64)

Supported Databases

The following databases have been tested in this release.

SQL Server 2000 with SP3 or later
SQL Server 2005 with SP2 or later

Notes:

SQL Server 7.0 is no longer supported. For SQL Server 7.0 support, use the legacy version of Toad 3.2.
SQL Server Compact Edition is not supported.

Additional

.NET Framework
Microsoft .NET Framework 2.0 with SP1 or later

Maintenance Plans

To take advantage of Integration Services (SSIS) in maintenance plans, you must install Integration Services on any instance where you want to create maintenance plans.

Citrix Requirements

Toad has been tested for Citrix support on Windows Server 2003 Enterprise Server SP2 using the MetaFrame Presentation Server 4.0 and Citrix Presentation Server Clients 10.2. For information about installing Toad in a Citrix environment, 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.0 Configuration.

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.

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.

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 2.0 or later

For information about installing Toad silently, see Install Toad Silently in the Toad for SQL Server 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 SP2 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.

SQL Server 2005 Prerequisites

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

Install the SQL Server 2005 Workstation Component option of the SQL Server 2005 installation.
In Toad, commit or rollback the connection 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.

In Toad, commit or rollback the connection before starting the debugging session.

SQL Server 2000 Prerequisites

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

Make sure that SQL Server 2000 with SP3 or SP4 is installed.
In Toad, commit or rollback the connection 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 SP3 or SP4 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.

In Toad, commit or rollback the connection before starting the debugging session.

Platforms Tested for Debugging Support

The following platforms have been tested for debugging support.

Note: The Service Pack on the client must match the Service Pack on the server unless specified otherwise.

SQL Server 2005 Platforms Tested for Debugging Support
Client	Server
Client	2003 EE	2003 EE (SP1)	2000 (SP4)	2000 Pro (SP4)	XP Pro	XP Pro (SP2)
2003 EE	—	—	—	—	—	—
2003 EE (SP1)	—	X	X	X	—	X
2000 (SP4)	—	X	X	X	—	X
2000 Pro (SP4)	—	X	X	X	—	X
XP Pro	—	—	—	—	—	—
XP Pro (SP2)	—	X	X	X	—	X
Vista Pro	—	—	—	—	—	—

SQL Server 2000 (SP4) Platforms Tested for Debugging Support
Client	Server
Client	2003 EE	2003 EE (SP1)	2000 (SP4)	2000 Pro (SP4)	XP Pro	XP Pro (SP2)
2003 EE	X	—	—	—	—	—
2003 EE (SP1)	—	X	—	—	—	—
2000 (SP4)	—	—	X	—	—	—
2000 Pro (SP4)	X	X	X	X	X	X
XP Pro	X	X	X	X	X	X
XP Pro (SP2)	X	X	X	—	—	X (Local server)
Vista Pro	—	—	—	—	—	—

SQL Server 2000 (SP3) Platforms Tested for Debugging Support
Client	Server
Client	2003 EE	2003 EE (SP1)	2000 (SP4)	2000 Pro (SP4)	XP Pro	XP Pro (SP2)
2003 EE	X	—	—	—	—	—
2003 EE (SP1)	—	X	—	—	—	—
2000 (SP4)	—	—	X	—	—	—
2000 Pro (SP4)	X	X	X	X	—	—
XP Pro	X	X	X	X	X	—
XP Pro (SP2)	—	—	—	—	—	X (Local server)
Vista Pro	—	—	—	—	—	—

SQL Server 2000 (SP3a) Platforms Tested for Debugging Support
Client	Server
Client	2003 EE	2003 EE (SP1)	2000 (SP4)	2000 Pro (SP4)	XP Pro	XP Pro (SP2)
2003 EE	—	—	—	—	—	—
2003 EE (SP1)	—	X	—	—	—	—
2000 (SP4)	—	—	X	—	—	—
2000 Pro (SP4)	X	X	X	X	—	—
XP Pro	—	—	—	—	—	—
XP Pro (SP2)	—	—	—	—	—	—
Vista Pro	—	—	—	—	—	—

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.

Installation

Installation Instructions

For general installation information, refer to the Installation Guide available from the Windows Start menu under Program Files | Quest Software | Toad for SQL Server 4.1 | Documentation.

For More Information

Contact Quest Software:

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.

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.

This document contains proprietary information protected by copyright. The software described in this document 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 purchaser’s personal use without the written permission of Quest Software, Inc.

If you have any questions regarding your potential use of this material, contact:

Trademarks

Quest, Quest Software, the Quest Software logo, Benchmark Factory, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, GPOAdmin, I/Watch, Imceda, InLook, IntelliProfile, InTrust, Invertus, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, MessageStats, NBSpool, NetBase, Npulse, NetPro, PassGo, PerformaSure, Quest Central, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, vAnalyzer, vAutomator, vControl, vConverter, vEssentials, vFoglight, vMigrator, vOptimizer Pro, vPackager, vRanger, vRanger Pro, vReplicator, vSpotlight, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vEssentials, 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 guide are property of their respective owners.

Disclaimer

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.

Feature	Resolved Issue	Defect
Installation/Upgrades	Attempting to resize a window in Toad when installed on a Windows Server 2003 64-bit computer no longer results in a "Error creating window handle" error.	ST#49069
	During a silent install, Toad now deploys the Connection.xml file, which contains pre-defined connections.	ST#48364
	You can now install Toad in a directory that includes Unicode characters in the directory name.	ST#52851
Automation	You can now execute automation scripts that were created using Toad for SQL Server 3.x.	ST#54918
Automation	You can now run a 3rd party program with optional command-line arguments using the Run Program activity.	ST#42944 CR#228672
Data Compare	When synchronizing varchar and char columns that have a null value, Data Compare now inserts a null value instead of an empty string “”.	ST#53433
Data Grid	Copying a row that has at least one column with a null value no longer results in an "Object reference not set to an instance of an object" error.	ST#53742
	When adding data to a column that has an Identity Increment value, Toad now correctly increments the value.	ST#41467 CR#117786
	Toad now inserts a decimal number correctly when using a European locale.	ST#53551
Editor	When sending a script to the editor from another area in the application such as the Object Explorer, the cursor now displays at the beginning of the script.	ST#50155
	The following Code Completion issues have been resolved: You no longer have to specify a database or owner to display a list of tables in Code Completion. If your query contains a WITH(NOLOCK) table hint, Code Completion now displays column names correctly. If you enter an @ symbol followed by a space, and then select an object from Code Completion that starts with an @ symbol, duplicate @@ symbols no longer display. If your query contains a SELECT count(*) statement, Code Completion now displays table names correctly. Code Completion now works with UPDATE and DELETE statements that use aliases.	ST#53545 ST#53044 ST#54755 ST#54538 ST#50365
	You can now right click the Messages tab of the script result and select Include Results to include script results in a text format below any output messages. Notes: This option is only available when you select Text Output for messages. If you include results in this tab, results still display in the Result Sets tab.	ST#41964 CR#207932
	Queries that contain a number of output messages no longer hang Toad.	ST#50235
Export Wizard/ One Click Export	All data export formats now support International characters.	ST#49830
Import Wizard	You can now import data that contains International characters from Excel.	ST#49831
Import Wizard	You can now import large data sets from Excel (approximately 650,000 rows) without experiencing performance issues.	ST#42321 CR#219754
Knowledge Xpert	If you purchased a copy of Toad that includes Knowledge Xpert, it is now enabled when upgrading Toad.	ST#55260
Object Explorer/ Database Browser	When selecting a different object from the Object Explorer tree, the object toolbar now updates without a delay.	ST#55268
	You no longer set the default object list display format (Tabbed, Tree view, or Drop-down) from the Options window. Instead, you now set the default from the drop-down list in the Object Explorer toolbar (far right of the object toolbar) and it is saved for future sessions.	ST#45363
	You can now apply or remove a named database or object filter by selecting a drop-down arrow beside the filter icon.	ST#42900 CR#228419
	Databases: Toad provides improved stability when working with tables with a large number of indexes.	ST#55583
	Tables: You can double-click constraints in the Specify Constraint Columns and the Specify Referenced Columns windows to add or remove them from the list. When altering the name and data type of a table column that has a description, a "Property cannot be added" error no longer displays.	ST#53072 ST#54805
	Procedures: If you run a stored procedure (right-click menu) that contains parameters with a DateTime data type, the Value field displays correctly. Selecting a varchar field in some instances from the Set Parameter window no longer results in a System.ArgumentOutOfRangeException error.	ST#51346 ST#54378
	Maintenance Plans: (SQL Server with LiteSpeed 4.x engine installed) You can now edit a LiteSpeed Back Up Database or Clean Up Maintenance Plan task for an SSIS maintenance plan if the LiteSpeed engine has not been upgraded to 5.0.	ST#52548
Query Builder	The following issues have been fixed for reverse engineering SQL from the Query tab or the Editor An Inner Join is no longer changed to a Cross Join when reverse engineering a query. The Diagram tab correctly models a Group by clause on a calculated column.	ST#52569 ST#48258
Quest Tools	You no longer have to open an editor window to access products in the Quest Tools submenu.	ST#55297
Reports	In the Reports Manager, you can now run the "Total Rows and Space Used" report for SQL Server 2005.	ST#52680
SQL Optimizer	Previously, you could right-click an open SQL Optimizer tab and a Change Connection option was available from the menu. Because the SQL Optimizer does not use Toad connections, selecting a different connection had no effect so this option has been disabled. For additional resolved issues and enhancements in the SQL Optimizer, see the SQL Optimizer release notes.	ST#53450

Email	info@quest.com
Mail	Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA
Web	http://www.quest.com

Contents

Welcome to Toad for SQL Server

New in This Release