|
|
Release Notes
Version: 2.0.3 Revised: October 2, 2006 ฉ 2006 Quest Software, Inc. All Rights Reserved.
|
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.
Support for SQL Server 2005 features and T-SQL debugging.
Create LIKE support for tables.
Click the red (read-only) indicator in a table's data grid to edit the data in tables that do not contain a primary key.
Generate and format data reports.
Enhanced schema reports.
Create multi-dimensional data views by dragging and dropping column headings to move data around. This provides an easy interface for viewing/slicing and dicing/reporting of data.
View or edit data from one or more tables that contain constraints.
Code Snippet ImprovementsInsert any code snippet into the Editor using the shortcut name and pressing CTRL+SPACE. The Code Snippets tool window now functions as an editor where you can add, rename, and delete snippets.
Macro Record/PlaybackRecord a series of keyboard commands in the Editor that can be played back multiple times.
Find and Replace in FilePerforms a Find and Replace across multiple files found in a directory structure.
Check CodeChecks whether the syntax is valid without executing the SQL.
Verify CodeChecks whether the syntax is valid, executes the code, and then undoes any changes to the code object and data.
Easily add, remove, start, or stop services from Toad.
Ability to restrict access to specific features in Toad.
Support for Microsoft Excel.
Provides asynchronous communication between applications on SQL Server instances.
Quickly recover data bin transaction logs.
Configure external tools to easily launch them from Toad.
Verify that your system meets the following minimum requirements.
|
Type |
Requirement |
|
Processor |
600 MHZ minimum |
|
Disk Space |
115 MB of disk space for installation Note: The disk space required may vary based on the edition of Toad selected for installation. |
|
Memory |
512 MB of RAM minimum, 768 MB recommended Note: The memory required may vary based on the following:
|
|
Monitor |
SVGA with a minimum resolution of 800x600, 1024x768 recommended |
|
Type |
Requirement |
|
Operating System |
Microsoftฎ Windowsฎ 2000, XP Professional, 2003 |
|
.NET Framework |
Microsoft .NET Framework 2.0 |
|
Browser |
Microsoft Internet Explorer 5.0.1 or later |
|
PDF Viewer |
Adobeฎ Acrobatฎ Reader 5.0 or later (for viewing the Getting Started Guide) |
|
Type |
Requirement |
|
Database Versions |
Microsoft SQL Server 2000 with SP3, 2005 |
|
Miscellaneous |
Microsoft SQL-DMO 8.0 (included if client connectivity is installed) |
|
Note: Client connectivity and configuration for each database is a pre-requisite for connecting. |
|
The following user privileges are required for installing and running Toad:
Only Power users and Administrators can install Toad.
If a Power user installs Toad, a Restricted user can run the application but cannot see the desktop icon or menu options 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, they can share desktop icons and menu items with any user on the computer.
Network and LAN installations are currently not supported.
In order to set or modify Toad Security settings, users must have privileges to create the QuestSoftware.ToadSecurity table if it does not exist. If the table does exist, users must have privileges to insert, update, and delete the QuestSoftware.ToadSecurity table.
Note: Currently, you cannot debug SQL/CLR code.
Verify the following general requirements to ensure that the Debugger will work 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.
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.
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.
On the client machine, install the SQL Server 2005 Workstation Component 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:
regsrv32 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 login must be a member of the SQL Server sysadmin group on the computer where Toad is installed and the computer where SQL Server 2005 is installed.
Your Database login (Windows or SQL Server Authentication used when connecting to SQL Server 2005) must be a member of the sysadmin role. To add your Windows login to the sysadmin role, execute the following:
sp_addsrvrolemember 'Domain\Name', 'sysadmin'
where Domain\Name is your Windows login
In Toad, commit or rollback the connection before starting the debugging session.
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 Debugging Support |
||||||
|
Client
|
Server |
|||||
|
2003 EE |
2003 EE (SP1) |
2000 |
2000 Pro (SP4) |
XP Pro |
XP Pro (SP2) |
|
|
2003 EE |
|
|
|
|
|
|
|
2003 EE (SP1) |
|
X |
X |
X |
|
X |
|
2000 |
|
X |
X |
X |
|
X |
|
2000 Pro |
|
X |
X |
X |
|
X |
|
XP Pro |
|
|
|
|
|
|
|
XP Pro (SP2) |
|
X |
X |
X |
|
X |
|
SQL Server 2000 (SP4) Debugging Support |
||||||
|
Client O/S |
Server O/S |
|||||
|
2003 EE |
2003 EE (SP1) |
2000 |
2000 Pro (SP4) |
XP Pro |
XP Pro (SP2) |
|
|
2003 EE |
X |
|
|
|
|
|
|
2003 EE (SP1) |
|
X |
|
|
|
|
|
2000 |
|
|
X |
|
|
|
|
2000 Pro |
X |
X |
X |
X |
X |
X |
|
XP Pro |
X |
X |
X |
X |
X |
X |
|
XP Pro (SP2) |
X |
X |
X |
|
|
X |
|
SQL Server 2000 (SP3) Debugging Support |
||||||
|
Client
|
Server |
|||||
|
2003 EE |
2003 EE (SP1) |
2000 |
2000 Pro (SP4) |
XP Pro |
XP Pro (SP2) |
|
|
2003 EE |
X |
|
|
|
|
|
|
2003 EE (SP1) |
|
X |
|
|
|
|
|
2000 |
|
|
X |
|
|
|
|
2000 Pro |
X |
X |
X |
X |
|
|
|
XP Pro |
X |
X |
X |
X |
X |
|
|
XP Pro (SP2) |
|
|
|
|
|
X |
|
SQL Server 2000 (SP3a) Debugging Support |
||||||
|
Client
|
Server |
|||||
|
2003 EE |
2003 EE (SP1) |
2000 |
2000 Pro (SP4) |
XP Pro |
XP Pro (SP2) |
|
|
2003 EE |
|
|
|
|
|
|
|
2003 EE (SP1) |
|
X |
|
|
|
|
|
2000 |
|
|
X |
|
|
|
|
2000 Pro |
X |
X |
X |
X |
|
|
|
XP Pro |
|
|
|
|
|
|
|
XP Pro (SP2) |
|
|
|
|
|
|
Please review important installation and upgrade information in the Getting Started Guide available from the Windows Start menu under Program Files | Quest Software | Toad for SQL Server 2.0 | Documentation.
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:
Toad for SQL Server Xpert Edition ONLY -- other versions of Toad SQL Server (Standard, Professional) are fine.
The SQL Optimizer feature does not support non-ASCII characters properly: display, processing, and editing of scripts in SQL Optimizer 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 Optimizer does not support multi-byte processing or display and should not be used with multi-byte scripts or data.
Toad Editions that contain Knowledge Xpert.
The Knowledge Xpert feature is available with English language content only.
The following issues have been resolved in this release of Toad for SQL Server.
|
Component |
Enhancement/Resolved Issue |
Case ID/ Change Request |
|
DB Browser/ Obj Palette |
Switching from Processes to Locks under Activity no longer results in an error. |
CR0188862 |
|
Editor |
Resolved an issue with the parser that resulted in an ArgumentOutOfRange error. |
CR0189662 |
|
Supported bind variable formats are now ignored when quoted. |
CR0188832 |
|
|
Log Reader |
The Log Reader now includes fully qualified object names so it can be used on SQL Server 2005. |
CR0189937 |
|
The Owner/Schema name is now included in the following:
|
CR0167708 |
|
|
Varchar and nvarchar values now display in the Log Reader. |
CID449114 |
|
|
Money and Smallmoney datatypes now display the correct values. |
CR0192107 |
|
|
Data is no longer truncated in the log file for SQL Server 2000. |
CR0189939 |
|
|
On SQL Server 2005, BINARY values can now be reconstructed for UPDATE operations. |
CR0191901 |
|
|
The DML/DDL tab now:
|
CR0191906 |
|
|
Options |
The search feature in the Options window now returns results for all pages. |
CR0191531 |
|
SQL Modeler |
Saved model files from the 1.0 release can now be opened in the 2.0 release. |
CID455708 |
|
Component |
Enhancement/Resolved Issue |
Case ID/ Change Request |
|
DB Browser/ |
Resolved a performance issue when displaying data in the Data tab. |
CR0180112 |
|
Resolved a performance issue that occurred when the msdb.dbo.backupset table contained 1000+ rows. You can further improve performance after applying this patch by clearing the Enable database backup checking under Tools | Options | Database | SQL Server. |
CID449965 |
|
|
Editor |
Resolved a memory leak in the Script Results data grid which affected performance. |
CR0186975 |
|
Export Wizard |
The Export wizard now supports exporting INSERT statements with decimal data when the decimal separator is a comma. |
CID449125 |
|
Options |
An error no longer occurs after selecting the Disable all caching checkbox in Tools | Options | Database | SQL. |
CR0188268 |
|
SQL Tuning |
For a list of resolved issues in this release, refer to: http://www.toadsoft.com/toadsqlserver/SQL_Tuning_for_SQL_Server_ |
|
|
Component |
Enhancement/Resolved Issue |
Case ID/ Change Request |
|
Export Wizard/ |
The correct file encoding format is now applied when exporting or importing files. |
CID436008 |
|
Import Wizard |
An error no longer occurs when importing a file where the regional setting for short date on the client does not match the DATEFORMAT setting on the database server. |
CR0184058 |
|
Component |
Enhancement/Resolved Issue |
Case ID/ Change Request |
|
General |
A threading error no longer locks Toad if left idle for an extended period of time. |
CID396214 |
|
DB Browser/ Obj Palette |
In Tree view, attempting to select Filegroups, Files, or Scripts from the "Current" node no longer results in an exception error. |
CR0137393 |
|
When altering a column in a table, you can now modify whether the column accepts null values. |
CID384449 |
|
|
When generating DDL for a database, unique constraints are now included in the DDL script. |
CID386637 |
|
|
When generating a data script for a database, Long text fields are now supported. |
CID390627 |
|
|
When creating a job step, selecting a database other than the default and then creating a SELECT statement on an existing table in that database no longer results in an error. |
CR0139781 |
|
|
Data Compare |
The synchronization script for each table no longer has a storage limit of 5 MB. |
CR0142210 |
|
Data Grid |
You can now edit data for tables that do not contain a primary key by clicking the red, read-only indicator (bottom left of the data pane) to open a custom key editor. You can modify settings options or accept the defaults to allow editing of data in the grid. |
CID398999 |
|
Debugger |
Debugging some stored procedures no longer results in an sp_procedure_param_rowset error. |
CID431294 |
|
The debugger now highlights the correct row to debug and displays breakpoints in the correct location. |
CID428887 |
|
|
Editor |
COMPUTE BY statements are not supported in this release, due to a limitation with the ADO.NET provider. |
CR0105196 |
|
Tables or columns that include the word go, such as a table name "goals," are no longer treated as keywords and parsed. |
CID378475 |
|
|
Code is now formatted properly when the WITH(NOLOCK) option is included in the statement. |
CID386983 |
|
|
Formatting a script and then attempting to view the explain plan no longer results in an error message displaying or the explain plan hanging. |
CR0134422 |
|
|
Export Wizard |
You can now set an identity_insert on and specify an explicit column list on the generated script. |
CID408101 |
|
Object Search |
After searching a database, right-clicking a trigger in the result set and selecting Generate DDL no longer results in an error. |
CID407062 |
|
Options |
The "Fetch data in background" option (Tools | Options | Browser | General) is now available in Toad for SQL Server. |
CR0120679 |
|
Schema Compare |
Dependencies in generated synchronization scripts are now ordered correctly. |
CID388327 |
|
SQL Modeler |
The correct syntax now displays in a generated query when using a cross join. |
CR0132231 |
|
Joining three tables no longer creates a cross join. |
CID401665 |
|
|
The SQL modeler now supports case sensitivity. |
CID398727 |
|
|
Table aliases now persist when using WHERE and OR conditions. |
CID393995 |
|
|
SQL Tuning |
For a list of resolved issues in this release, refer to: http://www.toadsoft.com/toadsqlserver/SQL_Tuning_for_SQL_Server_ |
|
The following issues have been identified in this release of Toad for SQL Server.
|
Component |
Known Issue |
Case ID/ |
|
Code Snippets |
When creating a new snippets folder, an exception error occurs if you do not rename the folder. |
CR0164885 |
|
Connection |
Attempting to launch Toad results in a System.Security.Policy.PolicyException error. To resolve this issue, ensure that the system administrator has placed Toad in the correct code group with permissions set to execute code. |
CID408845 |
|
If the status bar is hidden, attempting to connect to a database using Toad results in a "Parameter is not valid" error. As a workaround, right-click the toolbar area in the main Toad window and enable the Statusbar. |
CR0189787 |
|
|
Data Compare |
Currently, you can compare indexed views, but you cannot synchronize them. |
CR0166497 |
|
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. |
CR0142208 |
|
|
During synchronization, you should disable script options for triggers, dropping primary and foreign keys, etc. until the sync is complete under Tools | Options | Data Compare | Script. |
CR0142211 |
|
|
Database Browser/ Obj Palette |
After creating a database role and login and denying permission for creating a table on that login as well as giving the login the db_denydatabasereader role, attempting to create a table results in an error. |
CR0179445 |
|
When generating a data script for a database, CLR objects are not supported. |
CR0169708 |
|
|
The Deps (Uses) & Deps (Used by) tabs display as empty if an extended stored procedure is used. |
CR0117189 |
|
|
Currently, you cannot unbind a column from a rule if the table owner is not "dbo." |
CR0142201 |
|
|
When adding columns to a table, Toad does not increment the Identity Increment value properly. |
CR0117786 |
|
|
Attempting to view the error log in SQL Agent Properties on SQL Server 2005 results in an error. |
CR0167581 |
|
|
Debugger |
After entering start parameters for a remote debugging session on SQL Server 2005, a "CoUnmarshalInterface failed with error code 0x80040155" may display. To resolve this issue:
|
CR0166022 |
|
Quoted object names are not supported when using the Debugger. |
CR0125691 |
|
|
Editor |
Toad cannot execute an SQL script in the Editor if syntax highlighting is disabled (Tools | Options | Editor | Highlighting Styles). |
CR0167980 |
|
The following object types are not found when using the View Object at Cursor feature:
|
CR0164917 |
|
|
ClickingClear All Filters in the Editor toolbar does not take effect. As a workaround, click Define Filters and clear the filter manually, or open the Database Browser/Object Palette, and click Clear All Filters. |
CR0189718 |
|
|
Currently, the same parameter name cannot be used more than once for multiple tables in a query. |
CR0163853 |
|
|
Export Wizard |
Currently, the Export wizard does not support binary data types. |
CID419715 |
|
Help |
The following new features and enhancements have limited documentation in this release. This documentation will be expanded in a future release.
|
|
|
Log Reader |
In some environments, attempting to refresh the Log Reader may result in one of the following errors:
|
CID450811 |
|
If a database was backed up with the Overwrite option set to Append to media, the Log Reader is unable to read any appended changes. As a workaround, back up the database with the Overwrite option set to Overwrite existing media. |
CR0192659 |
|
|
Object Search |
Currently, you cannot search Unicode databases. |
CR0166781 |
|
Schema Compare |
Extended properties for a trigger do not display in the Results pane. |
CR0137005 |
|
Users with different names that share the same login are not synchronized correctly. |
CR0103387 |
|
|
Server Compare |
When running MSDE 2000, attempting to retrieve information from DTS Packages may result in a "General Repository Error: 80041035." |
CR0142205 |
|
If the target server is configured with Use Windows NT Fibers, you will not be able to synchronize Meta Data Service Packages. |
CR0142206 |
|
|
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. |
CR0142207 |
|
|
Currently, you cannot rollback Meta Data Service DTS Packages. |
CR0122712 |
|
|
Version Control |
Some error messages are currently available with English language content only. |
CR0140084 |
The following third party issues have been identified in this release of Toad for SQL Server.
|
Component |
Resolved Issue |
Case ID/ |
|
Export Wizard |
In order to export to an Office 2003 Excel instance, the Office 2003 Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from: http://www.microsoft.com/downloads/details.aspx?FamilyID=3c9a983a-ac14-4125-8ba0-d36d67e0f4ad&DisplayLang=en |
CR0138239 |
|
Help |
After installing Microsoft Security Update 896358, selecting a topic in the help file when using the Web Browser (Internal Help) results in the topic displaying in the navigation pane. Quest recommends using External Help (Tools | Options | Environment | Interface) as a workaround. 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. |
CR0129554 |
|
After installing Microsoft Security Update KB922616, attempting to view the Help file from the Web Browser (Internal Help) results in the following error: "COM object that has been separated from its underlying RCW cannot be used." Quest recommends using External Help (Tools | Options | Environment | Interface) as a workaround. If you want to use Internal Help, you will need to disable some features in the security update. Refer to Microsoft Security Bulletin MS06-046: http://www.microsoft.com/technet/security/Bulletin/MS06-046.mspx |
|
|
|
Version Control |
Quest recommends using the native VSS implementation in Toad rather than VSS via SCC integration. When using VSS via SCC, if the file does not have the attributes that SCC expects, there may be issues with the file being updated properly. |
CR0138078 |
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
You can join the Toad for SQL Server discussion group by sending an email to: toadss-subscribe@yahoogroups.com
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.