Quest® SQL Optimizer for Sybase
Version 3.0.0
Release Notes
February 8, 2008
It contains the following features:
Updates to Quest SQL Optimizer 3.0.0 for Sybase
New Features in Quest SQL Optimizer 3.0.0 for Sybase
Aggregated Functions - These new aggregated functions from Adaptive Server 15.0.2 are supported in the SQL parser and can be used throughout the modules in Quest SQL Optimizer: stddev, stddev_samp, stddev_pop, variance, var_samp, var_pop, stdev, stdevp, var, and varp.
Functions - These new functions from Adaptive Server 15.0.1 and 15.0.2 are supported in the SQL parser and can be used throughout the modules in Quest SQL Optimizer: rand2, authmech, hashbytes, hash, index_name, asehostname, reserve_identity, xa_bqual, xa_gtrid, isdate, isnumeric, and partition_object_id.
New Trigger Type - The INSTEAD OF TRIGGER type from Adaptive Server 15.0.2 is supported.
SET optimization criteria statement parameters - The ON, OFF, and DEFAULT parameters are supported for SET optimization criteria statement. Note: the optimization criteria are shown on the Criteria page of the "Optimization for ASE 15" page in the preferences window.
The following is a list of issues addressed and enhancements implemented in this release of Quest SQL Optimizer for Sybase.
|
Feature |
Resolved Issue |
Change Request |
| SQL Optimizer | An access violation error no longer occurs, if you open a saved Optimized SQL file, refresh the query plans in the Optimized SQL detail window, make the SQL Editor the active window, and then return to the Optimized SQL detail window. | CR0149219 |
| In the Batch Run, a SQL statement that is terminated because it ran longer than the termination time no longer shows a CPU time of zero. Instead the CPU time is displayed as blank so that it does not look like the fastest CPU time. | CR0149458 | |
| In the Batch Run when executing a SQL statement that is using a temporary table and you terminate the execution of one of the SQL statements, you no longer get an error about the temporary table not existing when each of the remaining SQL statements is executed. | SC565293 CR0227592 |
|
| The 'N/A is not a valid time' error message no longer occurs when you open a saved Optimized SQL file which has N/A saved in the one of the Time columns. | CR0149220 | |
| All charts which display the run time statistics now display the correct values, whereas some of them were showing zero instead of the correct value. |
CR0224770 |
|
| SQL statements that select data from a column datatype defined as "text" now execute instead of producing an error. |
SC493152 CR0204503 |
|
| When loading a saved Optimized SQL file, the Elapsed Time and CPU Time columns for either "All Records" or for "First n Records" are now showing blank instead of showing zeros for SQL statements that have not been executed. |
CR0163514 | |
| Occasionally, the Batch Run was failing to stop when you aborted it. This issue has been resolved. | CR0139394 | |
| SQL Inspector | An explanation of each QP Metrics statistic is now documented in the Help. | CR0153288 |
| When you have selected the Inspecting Approach of "Monitoring Tables", the Login Name, the Program Name, the Host Name, and Database Name are now shown with the statistics for each SQL statement. | CR0093500 | |
| Line numbers now appear with the statistics when each stored procedure extracted from the monitoring tables is not summed so that the run time statistics for each SQL in the stored procedure is displayed. |
SC465147 CR0193111 |
|
| Configuration Analyzer | The "max parallel degree" configuration parameter no longer produces an error when it is changed. | CR0185449 |
| SQL Scanner | The program no longer hangs when you are connected to the database with a user that does not have sa_role and you select the Abstract Plan Groups in the Add Jobs wizard. | CR0177708 |
| Abstract Plan | In the Abstract Plan Matrix, the tab for the XML plan no longer disappears when the alternative SQL statement is compatible with the original SQL statement. | CR0139383 |
| Integration with other Quest products | The file created to import SQL statements into the Benchmark Factory program now correctly assigns a bind variable to the SQL statement that it corresponds to instead of creating groups of bind variable together that would indicate that all of the SQL statements use the same variables. | CR0153352 |
| The message 'Failed to connect to "QCSYB_SQLTuning.exe" to DBSERVER...' no longer appears when you create a database connection profile for connecting to Adaptive Server as you are launching SQL Optimizer and then try to use it in Quest Central. | CR0172915 | |
| Index Advisor | An access violation error message no longer occurs after you have generated indexes, run the Batch Show Plan function, then created some user defined indexes and run the Batch Show Plan again for only your newly created index candidates. | CR0169995 |
| The "List index out of bounds" message no longer appears when you close the Index Advisor window when several index candidates are generated for a SQL statement. | CR0170453 | |
| SQL Repository | When the SQL statements are added to the SQL Repository using the "Add SQL from SQL Scanner" option, every database object now displays the correct database object name. |
CR0170203 |
| General | The program now works with an XP Secure Desktop. | SC349174 SC354720 SC378339 CR0128634 |
| Reports | When creating reports, you can now select individual SQL statements or a range of SQL statements for the report instead of only creating a report for all SQL statements. | CR0185444 |
The following is a list of issues known to exist at the time of Quest SQL Optimizer for Sybase release.
|
Feature |
Known Issue |
Change Request |
|||||||||||||||||||||||||
| General
|
Quest SQL Optimizer cannot terminate a database connection or an operation when the Adaptive Server transaction log is full. Thus, if the transaction log becomes full while you are using Quest SQL Optimizer, the program may hang. This only happens if the Adaptive Server ‘abort tran log full’ option is set ON. Workaround – Dump the transaction log. Or, you may set the Adaptive Server 'abort tran on log full' option OFF. You must evaluate whether this is an appropriate setting for your database environment. |
|
|||||||||||||||||||||||||
SQL statements that contain "INTO x PARTITION BY" clause are not supported. For example: select * |
CR0141739 | ||||||||||||||||||||||||||
The information for some datatypes does not display when records are retrieved from the database. This occurs on the Data tab of the Database Explorer module, the Run Results window in the SQL Optimizer module, and on the Result panel of the SQL Worksheet module. The following table lists the datatypes that do not display.
|
|||||||||||||||||||||||||||
|
The “WITH INTO_OPTION” syntax in the INTO clause of a SELECT SQL statement is not support. |
|
||||||||||||||||||||||||||
| SQL Inspector | The data files from SQL Tuning version 2.7.1 or earlier are not compatible with version 3.0.0. Workaround: Contact Quest Support for an update to fix this problem. |
CR45762 | |||||||||||||||||||||||||
SQL Collector for Monitor Server |
The SQL Collector module only works with the Adaptive Server 15.n client. Quest SQL Optimizer will hang if you are using an earlier version of the client and you use this module. Quest SQL Optimizer may also hang if you do not have the Monitor Server connection information correctly entered. Check the Help file for the detail information for setting up the Monitor Server connection. Workaround: Install the Adaptive Server 15.n client. This client is installed when you install Quest SQL Optimizer for Sybase if there is not already an Adaptive Server client on your computer. |
||||||||||||||||||||||||||
|
Run Result Time |
When you have a SQL statement with parameters, the time from the Run Result function may not correspond with the actual run time for SQL in your application due to the substitution of actual values for the parameters by the Run Result function. |
|
|||||||||||||||||||||||||
|
Preferences |
The Preference settings from previous versions of SQL Tuning will not be transferred to the Preference settings for SQL Optimizer. You must customize all the option settings once again. | ||||||||||||||||||||||||||
|
One set of these preferences for optimization processing when connected to Adaptive Server Enterprise version 15, Optimization Criteria, is not fully supported. Currently, if you select any of the Optimization Criteria preferences and your SQL statement contains a semi-join while connected to Adaptive Server 15 GA and esd #1, the criteria are not rolled back between the creation of each SQL statement. Without the rollback, some of the following query plans are retrieved using optimization criteria that would not normally be set. This affects the results of the optimization process as it compares one query plan to another. Workaround – when connected to Adaptive Server Enterprise 15 GA, and esd#1 and your SQL statement contains a semi-join, use the Custom setting in the Intelligence Level, then unselect all of the Optimization Criteria and the Optimization Goals when you optimize a SQL statement. |
|
||||||||||||||||||||||||||
| Analyzer modules | In the Analyzer modules, if you rapidly click several times on the child node of an Analyzer you may receive an Access Violation error message or an "Error loading SQL. File may be lost or corrupted." error message. | CR0228704 | |||||||||||||||||||||||||
| In the Analyzer modules, a query plan from Adaptive Server Enterprise version 12.5.3 or earlier cannot be compared to a query plan from Adapter Server Enterprise version 15 or later. | |||||||||||||||||||||||||||
| XML Plan | Structure and details of the XML plan will vary according to which version Adapter Server Enterprise you are connected to. | ||||||||||||||||||||||||||
| Database Explorer | Database Explorer displays the following error message if the connection to Adaptive Server is lost, and repeated attempts are made to reconnect to the database: Failed to connect to database. Workaround – there is no workaround for this issue. Quest SQL Optimizer must be restarted. |
||||||||||||||||||||||||||
| For Indexes that were created with a "LOCAL INDEX" clause, the DDL for the index which is displayed in the Database Explorer module will be missing the " LOCAL INDEX " clause. | CR0141705 | ||||||||||||||||||||||||||
| SQL Optimizer | The "mismatch with original SQL error" text may appear in the Remarks column after executing the Batch Run for SQL alternatives that are semantically equivalent to the original SQL statement. There is an issue with ASE 15.n that when the ASE forces are applied to certain SQL statements that no results are retrieved from the database. There is also another issue when the COALESCE function is added to a SQL statement that no results are retrieved from the database. Workaround: You should disregard these alternatives. |
||||||||||||||||||||||||||
National Language Support
Note: These problems only arise if you type characters in the national language. If you are using the national Windows environment and type English text, these problems do not arise. |
The message "Failed to retrieve the query plan ..." is displayed when you 1) select "dump abstract plan" on the Optimization | Abstract Plan page of the preferences, 2) connect to a French language database, and 3) optimize a SQL statement that contains any of the French language characters that are not a part of the English language character set. | CR0229440 | |||||||||||||||||||||||||
| An "Invalid value for field column_name" error occurs when you have your Windows environment set to French and you execute a SELECT SQL statement that selects the data from a column that stores monetary values. | CR0229495 | ||||||||||||||||||||||||||
| When the table name, column name, or other database object contains any of the French language characters that are not a part of the English language character set, the table, column, or database object is displayed in the SQL statement as "garbage" characters in the SQL Text pane. | CR0148792 |
Before installing Quest SQL Optimizer for Sybase ensure your system meets the following minimum hardware and software requirements:
| Platform | 233 MHZ minimum |
| Memory | Minimum 512MB |
| Hard Disk Space | 67 MB |
| Operating System | Windows 2000, XP Professional, or Window Server 2003 |
| Browser | Microsoft Internet Explorer 6.0 or later |
| PDF Viewer | Adobe® Acrobat® Reader 5.0 or later (for viewing the Installation Guide) |
| Database Client | Quest SQL Optimizer will install a database client if one is not installed. |
| Database Server | Adaptive Server 11.0 and above is 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 Sybase release package contains the following products:
| 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.
© 2008 Quest Software, Inc.
ALL RIGHTS RESERVED.
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:
| Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656
Email: legal@quest.com |
Refer to our web site for regional and international office information.
Quest, Quest Software, the Quest Software logo, Benchmark Factory, LECCOTech, Quest Central, Spotlight, SQL Navigator, SQLab, Toad, T.O.A.D., and Toad World 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.
This product includes RSA encryption logic from http://www.crypto-central.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.