Toad® for SQL Server
Beta Version 5.0.0
Beta Release Notes
Released: January 29, 2010
With Toad, developers and database administrators can use a familiar, proven tool to manage databases. Toad empowers developers and administrators, of varying skill levels, to rapidly create and execute queries, automate database object management and develop SQL more efficiently.
(SQL Server 2008 only) Toad now supports Resource Governor functionality
under the Management node in the Object Explorer.

Note: Once created, the classifier
function displays in the Functions node for the selected database.


(SQL Server 2008 Enterprise and Development Editions only) You can now add a
filter to indexes in the Create/Alter Index window.

When exporting to an Excel file, if there are multiple tables, Toad now exports to a single file and adds each table as a separate worksheet within that file.
Toad now checks the directory you
are exporting to and if a file with the same name already exists,
the text of the Overwrite checkbox turns red as a warning so you can
either overwrite or rename the file. The Next button is also
disabled until you make a change.

If you select a single table to
export in the Export Wizard, you can specify a different name for
the worksheet than the actual table name.

Group Execute includes the following enhancements:
You now have the ability to execute a SQL
script against each specific database within each specific
instance of SQL Server. To do so, click the Databases
toolbar button to select individual databases for each
connection on which you want to execute the script. If this
button is not selected (default behavior), the script runs
against the current database context only.

You can also merge the results of the entire group execution into a single result set by clicking the Merge results toolbar button.

Note: There are some cases where merging is not possible, such as when the columns do not match. In these cases, the results display in separate result sets.


You can now open a new project or save a project using buttons on the Project Manager toolbar.



|
Feature |
Resolved Issue |
Change Request |
|
New in this Beta Drop |
||
|
ER Diagrammer |
ER Diagram: Cannot cancel the long running process. | CR67334 |
|---|---|---|
|
Debugger |
Debugging should be disabled for encrypted stored procedure/functions. | CR67503 |
|
FTP |
FTP Enhancement Request - Add an Explorer Style Folder Drop-down List. | CR64874 |
| Group Execute | Move Group Execute from instance-level only functionality to database-level functionality. | CR65552 |
| Not Saving Connection Information. | CR69348 | |
| Unavailable Connections Slow Down Group Execute. | CR68775 | |
|
Object Editor
|
Resource Governor: Resource Pool DOE implementation. | CR68609 |
| Resource Governor: Enable/Disable actions implementation. | CR68617 | |
| Resource Governor: Classification Function DOE implementation. | CR69742 | |
| Resource Governor: Workload Group DOE implementation. | CR68610 | |
| Resource Governor: Remove Classifier Function dialog. Suggestion to add option to drop user-defined function itself. | CR70310 | |
| Error altering table in SQL Server 2005. | CR68437 (Reported by cynthiarancho48) | |
| Run DBCC check table instead of using dynamic SQL for Check Tables. | CR67209 | |
| Hide Database drop-down in Rename dialogs for all objects. Add option to control to hide specific dropdowns. | CR67208 | |
| Filtered Indexes support (Index DOE). | CR68607 | |
| Logins: Option "User must change password at next login" is missing from SQL Server logins. | CR64957 | |
| Create Database: Impossible to set 'read only' for newly added filestream filegroup. | CR64023 | |
| Functions: Incorrect syntax is generated for Rename DOE. Schema is missing. | CR70557 | |
| Databases: Exception occurs when trying to click on Create Like DOE. | CR70624 | |
| Functions: Exception occurs when open Create like DOE. | CR70566 | |
| Tables: Exception when clicking on Create Statistics. | CR70476 | |
|
Object Explorer |
Resource Governor: LHS infrastructure support. | CR68608 |
|
Permissions |
Architecture and Appearance changes: Privilege Escalation Framework. | CR69267 |
|
Query Builder |
Upgrading non ansi outers (*= and =*) with ansi LEFT/RIGHT OUTER JOINs. | CR68128 |
|
Schema Compare & Sync |
Default Schema Snapshot Save Location Still Pointing to Program Files. | CR67763 |
|
UI |
Cannot remap keys in Toad. | CR69992 |
|
In Previous Beta Drops |
||
|
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: |
CR#216699 ST#42154 |
|
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.0 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.0 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 |
|
Editor |
The following object types are not found when using the View Object at Cursor (F4) feature:
|
CR#164917 ST#41627 |
|
By default, the Document recovery option is enabled in Tools | Options | Environment | General. If you select Allow multiple copies of Toad for SQL Server to be loaded checkbox on this page, it automatically disables the Document recovery option to avoid possible conflicts. |
N/A |
|
|
Export Wizard/ One Click Export |
Binary data types cannot be exported in this release. |
CR#170430 ST#41655 |
|
Import Wizard |
Currently, you cannot import Excel 2007 files because they are saved using an xlsx format. Workaround: |
CR#221667 ST#42416 |
|
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 |
|
(SQL Server with LiteSpeed 4.x engine installed) You cannot 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 |
|
|
Object Explorer/ Database Explorer |
Tables: Attempting to enter data for an XML data type in the Data tab results in an error. |
ST#42580 |
|
Query Builder |
When reverse engineering SQL from the Query tab or the Editor, consider the following:
|
ST#49731 |
|
Server Compare |
If the target server is configured with Use Windows NT Fibers, you cannot synchronize Meta Data Service Packages. |
CR#142206 |
|
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." |
CR#214601 ST#42093 |
|
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 2007 PIAs
|
CR#138239 |
|
Import Wizard |
Importing large data sets from Excel (approximately 650,000 rows) is not recommended because of the amount of time it may take. This issue occurs because the Excel import component maintains the output in memory until the import completes. This can cause performance issues depending on the available system resources. |
CR#219754 |
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
|
| Hard Disk Space | 133 MB of disk space for installation.
|
| Operating System |
Windows Server 2003 (32-bit or 64-bit) Windows XP Professional (32-bit or 64-bit) Windows Vista Windows Server 2008 Windows Server 2008 R2 (64-bit) Windows 7 |
| Additional Software | .NET Framework Microsoft .NET Framework 3.5 (Service Pack 1) Notes:
(Optional) Spotlight on SQL Server Spotlight on SQL Server 4.5 or later Web Browser PDF Viewer
Maintenance Plans Review the following requirements for using Maintenance Plans:
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. |
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 |
| Supported Databases |
The following databases have been tested in this release.
Notes:
|
| Additional |
.NET Framework Microsoft .NET Framework 3.5 (Service Pack 1) Maintenance Plans To take advantage of Integration Services (SSIS) in maintenance plans, you must install the following:
|
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.
The following user privileges are required for installing and running Toad for SQL Server:
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.
Verify the following general requirements to ensure that the Debugger operates properly for all SQL Server installations:
Note: The security policy can be applied to the domain or local computer.
Note: Currently, you cannot debug SQL/CLR code.
To debug locally, perform the following on the Toad client
To debug remotely, perform the following
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.
To debug locally, perform the following on the Toad client:
To debug remotely, perform 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
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.
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.
- Open a command prompt and run dcomcnfg.exe.
- Expand Component Services, Computers.
- Right-click My Computer and select Properties.
- Select the COM Security tab.
- 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.
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 Server—This 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.
You can join the Toad for SQL Server beta discussion group by sending an email to: toad_ss_beta-subscribe@yahoogroups.com
© 2010 Quest Software, Inc.
ALL RIGHTS RESERVED.
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 purchaser’s 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.
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.
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.