|
Release Notes Toad® for SQL Server
Version: 1.0.3 Revised: January 30, 2006 Copyright Quest ® Software, Inc. 2005-2006. All rights reserved.
|
Toad for SQL Server is a database development and administration solution that provides productivity features/functions 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.
Toad for SQL Server includes the following key features:
Quickly create, modify, execute, and save queries.
Customizable SQL and Procedure Editor provides advanced filtering, sorting, and grouping of data as well as options for organizing result sets.
Flexible Data Grids provide enhanced capabilities for viewing and saving data.
Quickly view, create, modify, and manage database objects.
Format the layout of code, including inserting headers, adding or removing extra lines, and changing the case for keywords (Not available in freeware).
Easily save extracted data from the database to different formats (Not available in freeware).
For a list of resolved issues in v1.0.3, refer to Resolved Issues.
Verify that your system meets the following minimum requirements.
Computer with a minimum of 233 MHz; 300 MHz or higher recommended
82 MB of disk space for installation
512 MB of RAM minimum, 768 MB recommended
VGA monitor with a minimum resolution of 800x600, 1024x768 is recommended.
Microsoft Windows 2000, Windows 2003, or Windows XP
Microsoft .NET Framework 1.1
Microsoft Internet Explorer 5.01 or later
Adobe Acrobat Reader 4.0 or later (for viewing the Getting Started Guide)
Client connectivity and configuration for each database (pre-requisite for connecting)
Microsoft SQL-DMO 8.0 (included if client connectivity is installed)
Microsoft SQL Server 7.0, 2000 with SP3, 2005
The following items are not checked by the Debugger Setup Wizard and may result in the Debugger failing to run:
Disable all firewalls or open corresponding ports. Windows XP SP2 includes an embedded Windows firewall that should be disabled or ports opened as well.
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 that the security policy can be applied to the domain or local computer.
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.
|
2003 EE Server |
2003 EE Server with SP1 |
2000 Server with SP4 |
2000 Pro Server with SP4 |
XP Pro Server |
XP Pro Server with SP2 |
2003 EE Client |
P |
— |
— |
— |
— |
— |
2003 EE Client with SP1 |
— |
P |
—
|
—
|
—
|
—
|
2000 Client with SP4 |
—
|
—
|
P |
—
|
—
|
—
|
2000 Pro Client with SP4 |
P |
P |
P |
P |
P |
P |
XP Pro Client |
P |
P |
P |
P |
P |
P |
XP Pro Client with SP2 |
P |
P |
P |
— |
— |
P |
|
2003 EE Server |
2003 EE Server with SP1 |
2000 Server with SP4 |
2000 Pro Server with SP4 |
XP Pro Server |
XP Pro Server with SP2 |
2003 EE Client |
P |
— |
— |
— |
— |
— |
2003 EE Client with SP1 |
— |
P |
—
|
—
|
—
|
—
|
2000 Client with SP4 |
—
|
—
|
P |
—
|
—
|
—
|
2000 Pro Client with SP4 |
P |
P |
P |
P |
—
|
—
|
XP Pro Client |
P |
P |
P |
P |
P |
— |
XP Pro Client with SP2 |
—
|
—
|
—
|
—
|
— |
P |
|
2003 EE Server |
2003 EE Server with SP1 |
2000 Server with SP4 |
2000 Pro Server with SP4 |
XP Pro Server |
XP Pro Server with SP2 |
2003 EE Client |
— |
— |
— |
— |
— |
— |
2003 EE Client with SP1 |
— |
P |
—
|
—
|
—
|
—
|
2000 Client with SP4 |
—
|
—
|
P |
—
|
—
|
—
|
2000 Pro Client with SP4 |
— |
— |
— |
— |
—
|
—
|
XP Pro Client |
— |
— |
— |
— |
— |
— |
XP Pro Client with SP2 |
—
|
—
|
—
|
—
|
— |
— |
The platforms and configurations supported in this release can use any time zone, character encoding, language, or locale configuration to operate this product. Toad for SQL Server supports multi-locale operation and uses the Unicode character set internally to support simultaneous operation with multilingual data. This release has been tested with the following language and platform combinations in addition to U.S. English:
Windows 2000 Professional (French server and client) on SQL Server 2000 (French)
Windows 2000 Professional (German server and client) on SQL Server 2000 (German)
Windows XP Professional (French server and client) on SQL Server 2000 (French)
Windows XP Professional (German server and client) on SQL Server 2000 (German)
The following limitation has been identified in the Toad Xpert Edition:
The SQL Tuning feature does not support non-ASCII characters properly: display, processing, and editing of scripts in SQL Tuning may result in improper display of data and in some cases, unintentional data degradation. Support for Western European or other single-byte Windows code pages and/or configurations may work appropriately, but these configurations have not been thoroughly tested and this portion of the product should be used with caution in these environments. SQL Tuning does not support multi-byte processing or display and should not be used with multi-byte scripts or data.
The following limitation has been identified in the Toad Professional Edition:
The Knowledge Xpert feature is available with English language content only.
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 will not be able to see the desktop icon or menu options in the Windows Start menu. Restricted users can create a shortcut to the application and place it on their desktop from the install directory.
If an Administrator installs Toad, they can share desktop icons and menu items with any user on the computer.
Network and LAN installations are currently not supported.
Please review important installation and upgrade information in the Toad for SQL Server Getting Started Guide available from the Windows Start menu under Program Files | Quest Software | Toad for SQL Server | Documentation.
The following issues have been
resolved in this release.
Component |
Resolved Issue |
Change Request |
Object Search |
Performing an object search no longer results in a "Error: System.Runtime.InteropServies.COMExeption" error. |
CR152808 |
The following issues have been identified in this release.
Component |
Known Issue |
Change Request |
Uninstall |
Uninstalling Quest Central version 5.0.1 when Toad is installed results in a "Marshaler restriction: Excessively long string" error and Toad cannot run. As a workaround, uninstall and re-install Toad. |
CR125321 |
Help |
The internal help file uses an ActiveX control to enable cross-frame navigation in an internal browser window. Microsoft security update 896358 restricts the use of the ActiveX control due to potential vulnerabilities and results in the internal help topic displaying in the TOC or Index pane. If you want to use internal help, you will need to disable some features in the security update. Refer to Microsoft Knowledge Base article: http://support.microsoft.com/kb/896905/ for steps to re-enable these features in ActiveX. |
CR129554 |
SQL Modeler |
Currently, the SQL Modeler allows a JOIN condition for a cross join, which results in incorrect syntax in the Generated Query. |
CR132231 |
Editor |
COMPUTE BY statements are not supported in this release, due to a limitation with the ADO.NET provider. |
CR105196 |
Explain Plan |
An error message may display, or the explain plan may hang if you format a script and then attempt to view the explain plan. |
CR134422 |
Debugger |
Quoted object names are not supported when using the Debugger. |
CR125691 |
DB Browser/ Obj Palette |
In Tree view, attempting to select Filegroups, Files, or Scripts from the "Current" node results in an exception error. |
CR137393 |
DB Browser/ Obj Palette |
In Tree view, filtering does not function properly for: Databases, Logins, Alerts, Operators, Jobs, and System Datatypes. |
CR118351 |
DB Browser/ Obj Palette |
The Deps (Uses) & Deps (Used by) tabs display as empty if an extended stored procedure is used. |
CR117189 |
DB Browser/ Obj Palette |
Currently, you cannot unbind a column from a rule if the table owner is not "dbo." |
|
DB Browser/ Obj Palette |
You cannot add a new column to a table without selecting "Allow Nulls" and/or setting a "default-constraint." |
CR118639 |
DB Browser/ Obj Palette |
When adding columns to a table, Toad does not increment the Identity Increment value properly. |
CR117786 |
DB Browser/ Obj Palette |
When a table is dropped and another table is created with the same name, object detail tabs are not refreshed and display details for the dropped table. To resolve this issue, press SHIFT + F5. |
CR140014 |
DB Browser/ Obj Palette |
When creating a job step, if you select a database other than the default and create a SELECT statement on an existing table in that database, a dialog displays with the following message: "The following syntax errors were detected in the command: Invalid object name." error displays. You can click Yes to continue and can ignore this error message. To avoid this error message, specify the database name before the table in the SELECT statement. |
CR139781 |
DB Browser/ Obj Palette |
Attempting to generate a data script for a database that includes tables with empty rows results in some or occasionally all tables being excluded from the generated script. |
CR140007 |
Data Grid |
If a row contains more than 48077 bytes in a character-based column, an error occurs and a red X displays in the grid. |
CR124005 |
Options |
Currently, the option to Prompt for Comment when adding a new file is ignored. |
CR137118 |
Options |
The "Fetch data in background" option (Tools | Options | Browser | General) is not used in this release. |
CR120679 |
Schema Compare |
Currently, extended properties for a trigger do not display in the Results pane. |
CR137005 |
Schema Compare |
Users with different names that share the same login are currently not synchronized correctly. |
CR103387 |
Schema Compare |
If a script contains an invalid procedure/function/view, but does not break the transaction, an error does not display after executing the Run script immediately option. However, these objects are commented in case you selected the "Ignore invalid procedures, functions, and views" checkbox in Tools | Options | Schema Compare | Script. |
CR123707 |
Server Compare |
When running MSDE 2000, attempting to retrieve information from DTS Packages may result in a "General Repository Error: 80041035." |
CR142205 |
Server Compare |
When running SQL Server 2000 SP4 on a virtual machine, an exception error may occur when trying to synchronize a DTS package. |
CR137590 |
Server Compare |
If the target server is configured with Use Windows NT Fibers, you will not be able to synchronize Meta Data Service Packages. |
CR142206 |
Server Compare |
If the Meta Data Service DTS Packages contain a COM object that is not registered on the target server, you may receive an exception error during synchronization. |
CR142207 |
Server Compare |
Currently, you cannot rollback Meta Data Service DTS Packages. |
CR122712 |
Data Compare |
Quest recommends limiting compares to 20000 rows in tables. When using Data Compare on large databases, Quest recommends excluding tables with large data sets from the comparison. |
CR142208 |
Data Compare |
Currently, the synchronization script for each table displays using the SyntaxEditor component. This component has a storage limit of 5 MB, and should be disabled for large scripts. |
CR142210 |
Data Compare |
When synchronizing, you should disable script options for triggers, dropping primary and foreign keys, etc. until the sync is complete under Tools | Options | Data Compare | Script. |
CR142211 |
SQL Tuning |
Removing SQL Tuning from Toad or Quest Central disables SQL Tuning. |
CR138066 |
SQL Tuning |
When using SQL Tuning for SQL Server in Toad, you cannot connect to SQL Server using the local host. If you use <local> as the server name, the connection will fail. Instead, use the actual server name when connecting to the SQL Server database. |
CR142213 |
SQL Tuning |
Attempting to search the help file while in an open SQL Tuning window hangs Toad. |
CR138523 |
SQL Tuning |
Attempting to launch SQL Tuning without an explain plan results in Toad hanging. As a workaround, generate an explain plan prior to launching SQL Tuning. |
CR135762 |
Quest Software's world-class support team is dedicated to ensuring successful product installation and use for trial and commercial versions of Quest Software solutions.
SupportLink: www.quest.com/support
Email: support@quest.com
You can use SupportLink to do the following:
Create, update, or view support requests
Search the knowledge base
Access FAQs
Download patches
You can join the Toad for SQL Server discussion group by sending an email to: toadss-subscribe@yahoogroups.com