Quest® SQL Optimizer for SQL Server
Version 6.6.1
Release Notes
November 5, 2009
Quest SQL Optimizer for SQL Server is the most comprehensive optimization solution available for SQL Server environments. Some of its product highlights include:
Updates to Quest SQL Optimizer for SQL Server
Updates to Quest SQL Optimizer for SQL Server
The following is a list of issues addressed and enhancements implemented in this release of Quest SQL Optimizer for SQL Server.
|
Feature |
Resolved Issue |
Defect ID |
| Installation | You will no longer see the DOS command window appearing during the installation process. | ST#64825 |
| User-Defined Temp Table | On the Temp Table List tab, the drop-down list of temporary tables no longer displays "All" twice. | ST#64928 |
| Integration with other Quest products | After you have optimized a SQL statement sent from Toad and returned the SQL alternative to Toad, now when you are prompted to close Quest SQL Optimizer inside of Toad, the program will close as expected. | ST#66026 |
| If you install Toad for SQL Server and Quest SQL Optimizer and then uninstall Quest SQL Optimizer, you will no longer be able to send a SQL statement from Toad to Quest SQL Optimizer whereas before you would get an error when you tried to send a statement. | ST#67967 | |
| You will no longer receive the error message "Processing Error! SQL Server does not exist or Network Access is denied." when you are sending a SQL statement to Quest SQL Optimizer from Quest Performance Analysis or Spotlight when you connected to SQL Server using Windows authentication. | ST#65520 | |
| Tuning Lab | The error message "System Error. Code 1400. Invalid window handle." no longer appears when you drag the mouse pointer over any enable button on the toolbar to display the button tips. This occurred after opening a Tuning Lab, entering a SQL statement, closing the Lab, and then opening the Tuning Lab again. | ST#64833 |
| The text in the Alert window now correctly instructs you to use the Batch Run function instead of the Execute All function after you have completed the optimization or index generation process. | ST#65021 | |
| When you upgrade from Quest SQL Optimizer 6.5 or earlier, the default order of the columns in the Scenario Explorer window is now correct. | ST#65931 | |
| The Batch Run Multiple Times function now executes the SQL statements the number of times you specify when you clear the Set as default option as you are setting the number of times to execute the SQL statements. | ST#67688 | |
| The confirmation box for the Delete Scenario function is no longer hidden behind the Quest SQL Optimizer window. | ST#67538 | |
| An error in the calculation of the run time for the Run all SQL twice if original SQL runs faster than(seconds): 5 Execution option was corrected | ST#68175 | |
| The row count, which displays the number of records processed after a SQL statement is executed, now displays the correct number for the UPDATE, INSERT, DELETE, and MERGE SQL statements. Before it was displaying zero. | ST#66891 | |
| SQL Scanner | On Windows Vista 64-bit, you will no longer get an error when you are expanding the Database tree in the Database Objects page in the Add Jobs wizard. | ST#65070 |
| On Windows 7 64-bit, the buttons on the Scanned SQL Viewer window are no longer missing. | ST#67344 | |
| When you are running on a 64-bit operating system, you can now send a SQL statement from the Scanned SQL Viewer to the Tuning Lab. | ST#67345 |
The following is a list of issues known to exist at the time of Quest SQL Optimizer for SQL Server release.
|
Feature |
Known Issue |
Defect ID |
|
SQL Scanner |
When scanning a SQL repository in Quest Performance Analysis, the SQL Scanner only looks for a database with the name of Quest_Performance_Repository. If another name was used for the SQL Repository database, the Scanner will not find it. | ST#41320 |
| The SQL Server CURSOR_CLOSE_ON_COMMIT dboption parameter should be set to OFF. Otherwise when the system stored procedure sp_helptext is used in the SQL Scanner module, it may return the following error due to SQL Server BUG #: 57967 (SQLBUG_70) or BUG #:231137 (SHILOH): Server: Msg 16917, Level 16, State 2, Line 0 Cursor is not open. |
||
If the text in a SQL statement contains a control character [#0...#32] inside a quoted string, an error will occur when it is displayed in the Scanned SQL Viewer or when a report is generated. For example, this SQL statement contains control character 3: SELECT 'abc#3def' FROM EMPLOYEE |
ST#41369 | |
| The line number for the location of the SQL statement is not correct when the carriage return and line feed characters are split between two blocks in the source text. | ST#41370 | |
| When scanning SQL statements that use temporary tables and you are using the option to Include data, the INSERT, UPDATE, or DELETE statements that contain a parameter are not including the Scanner Temp Table page. | ST#47606 | |
| Tuning Lab | When the Database Setting parameter Set Quoted_Identifier is set to Off, a SQL statement that uses the DATEADD function receives an error when double quotes are used in the argument: DATEADD("yyyy",3) Workaround: Receiving this message is actually what should happen when Set Quoted Identifier is set to Off because to delimit identifiers and literal strings is the purpose of the quoted identifier setting. So if you use the quotes when the setting is set to Off you should get an error. To get rid of this error, you can remove the quotes around the argument. Or, in Preferences | Database Setting, you can set this parameter to either On or Use database default. |
|
| A SQL statement which has a hidden control character in the text of the SQL statement will be classified as an "Invalid SQL." | ST#41386 |
|
| When you load a saved session and then execute the alternatives, you will get an Invalid SQL statement message for all the SQL alternatives that are using temp tables. | ST#41344 | |
When a SQL statement that was sent to the Tuning Lab had the "Trigger Conversion" applied by the scanning process, the SQL statement that was used to create the trigger's temporary table is inserted into the SQL Text window along with the SQL statement. This causes an error when the Optimize, Generate Virtual Indexes, Get Plan or other functions are selected. Workaround: Delete the statement that creates the temporary table from the SQL Text window. |
ST#48663 | |
| When optimizing a SQL statement using the option: Optimization | Results | Check Compatibility to SQL-92 standard with Show Indicator, the SQL statements that are generated are only the ones that compatible with the SQL-92 standard (the same result as the Generate compatible SQL only option). The correct results should be all the possible rewrites with a note on the Alert window to indicate which SQL statements are compatible. | ST#48902 | |
| Help | If you open Help while you are in the Tuning Lab and use the Search function, Quest SQL Optimizer and Help will freeze. Workaround: Open help before entering the Tuning Lab module, from the SQL Scanner module, or from Start | All Programs | Quest SQL Optimizer for SQL Server | Documentation | Help. |
ST#68212 |
| Uninstall | If Toad for SQL Server is installed, the uninstall for Quest SQL Optimizer for SQL Server 6.6.1 will not be completed correctly. If you then reinstall Quest SQL Optimizer 6.6.0 (the previous version), it will not run. Workaround: 1. Uninstall Toad. |
ST#68016 |
| Limited User | If your Windows logon is set to a "Limited User", the slider on the Optimization | Intelligence and Index Expert | Intelligence option pages is always displayed at 0. Although the display shows 0, it will use the default setting of 4. | ST#68383 |
| Support Bundle | When running on Windows Vista, when you create the Zip file to send to Tech Support, you will get the error message: "Error - No files to Zip." | ST#48189 |
| Silent Installation on Vista | You cannot do a silent installation on a Windows Vista computer if the User Account Control (UAC) is set to ON. Workaround: Set the User Account Control to OFF.
|
ST#64274 |
| MSI Installation on Vista Enterprise | On Vista Enterprise if you run the MSI installer (double-click QuestSQLOptimzer_SQLServer_6.6.msi) with the User Account Control (UAC) set to ON, when you run Quest SQL Optimizer, you will receive this error: "Class not Registered". Workaround: Set the User Account Control to OFF.
|
ST#64478 |
| Installation in VM ware | If you install Quest SQL Optimizer for SQL Server under VM ware and you have printers installed, an error will occur when you exit the program. Workaround: Delete all the printers. |
Before installing Quest SQL Optimizer for SQL Server, ensure your system meets the following minimum hardware and software requirements:
| Platform | Pentium III 500 MHZ minimum |
| Memory | 512 MB of RAM minimum Note: The memory required may vary based on the following:
|
| Hard Disk Space | 1.3 MB of disk space for installation Note: This is the disk space required for a full installation, which includes 457 MB download of temporary setup files that can be removed at the completion of the installation. |
| Operating System | Microsoft Windows 2000 Microsoft Windows 2003 (32-bit) Microsoft Windows XP (32-bit) Microsoft Windows Vista (32-bit) Microsoft Windows 7 (32-bit) |
| Browser | Microsoft Internet Explorer 6.0 or later |
| PDF Viewer | Adobe Acrobat Reader 7.0 or later (for viewing the Installation Guide) |
| Database Server | Microsoft SQL Server 2000, 2005, or 2008 (32-bit) Note: SQL Server Compact edition is NOT supported. |
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 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.
The Quest SQL Optimizer for SQL Server release package contains the following products:
Refer to the Installation Guide for installation instructions.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA |
|
| Web |
Refer to our Web site for regional and international office information.
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:
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 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.
© 2009 Quest Software, Inc. ALL RIGHTS RESERVED.
Quest, Quest Software, the Quest Software logo, Benchmark Factory, Knowledge Xpert, Quest Central, Spotlight, Toad, and T.O.A.D. 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.
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 Email: legal@quest.com |
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.