Tuesday, July 18, 2017
SQL Optimizer contains the following features:
Quest SQL Optimizer for SAP® ASE 3.8.0 is a minor release containing several bug fixes and enhancements.
The following is a list of issues addressed and enhancements implemented in this release.
|Resolved Issue||Defect ID|
|Check Encrypt Password in the connection dialog to use Kerberos encryption for passwords||SOFS-148|
|Popup error “Tab index out of bounds” when switching from multiple scenario to a single one has been fixed||SOFS-122|
|Popup error “Tab index out of bounds” after creating a user defined SQL and clicking SQL Compare has been fixed||SOFS-114|
|Popup error “Integer overflow” when using SQL Scanner with a specific set of indexes as been fixed||SOFS-166|
|A bug concerning integration of Benchmark Factory and SQL Optimizer has been fixed||SOFS-123|
|Feature||Known Issue||Defect ID|
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 SQL Optimizer, the program may hang. This only happens if the Adaptive Server ‘abort tran log full’ option is set ON.
Dump the transaction log.
DUMP TRANSACTION database_name WITH TRUNCATE_ONLY
Or, you may set the Adaptive Server 'abort tran on log full' option to OFF. You must evaluate whether this is an appropriate setting for your database environment.
|The “WITH INTO_OPTION” syntax in the INTO clause of a SELECT statement is not supported.||ST45442|
The information for some data types 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 data type's that do not display.
On Windows Vista, the silent installation will not work if the Windows Vista parameter, Turn User Account Control, is on.
Set Turn User Account Control to off.
If you did not uninstall the previous version of SQL Optimizer before you installed the current version, the following message displays when you launch the program:
"The feature that you are trying to use is on a network resource that is unavailable."
Click OK to try again, or enter an alternative path to a folder containing the installation package ‘QuestSQLOptimizer_Sybase_version.msi’ in the box below."
You must uninstall the previous version of SQL Optimizer, and then install the current version again.
|SQL Collector for Monitor Server||Quest SQL Optimizer for SAP ASE may hang if you do not have the Monitor Server connection information correctly entered. Check the Help file for detailed information for setting up the Monitor Server connection.|
|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 versions of SQL Tuning prior to version 3.0 will not be transferred to the Preference settings for the current version. You must customize all the option settings once again.|
|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.||ST46539|
|In the Analyzer modules, a query plan from ASE 12.5.3 or earlier cannot be compared to a query plan from ASE 15 or later|
|XML Plan||Structure and details of the XML plan vary according to which version of ASE to which you are connected.|
Database Explorer displays the following error message if the connection to the Adaptive Server is lost, and repeated attempts are made to reconnect to the database:
Failed to connect to database.
Fatal error: in TISybDatabase.Logon
There is no workaround for this issue. SQL Optimizer must be restarted.
After you have executed the SQL alternatives in the Batch Run or individually, the “mismatch with original SQL error” message may display in the Remarks column in the Run Time pane in the SQL Optimizer window. This message indicates that the alternative is not retrieving the same result set as the original SQL.
This message should indicate that the alternative is not “semantically equivalent” and therefore is not a correct SQL transformation for the original SQL statement.
However, in closely looking at the SQL alternatives that sometimes produce this message, it can be seen that the SQL alternatives are semantically equivalent to the original SQL statement and should be retrieving the same result.
There are two issues that cause this error. The first is caused by an issue in ASE 15.x when the forces (see the Optimization Preferences) are applied to some of the SQL alternatives and the result is that no records are retrieved from the database.
The second is caused by a similar issue in ASE 15.x when the COALESCE function is added to some of the SQL alternatives and the result is that no records are retrieved from the database.
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.||ST46552|
|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.||ST46555|
|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.||ST46485|
Before installing Quest SQL Optimizer for SAP ASE, ensure your system meets the following minimum hardware and software requirements:
|Platform||1 GHz recommended minimum|
|Memory||1 GB of RAM recommended minimum|
|Hard Disk Space||100 MB hard disk space|
Microsoft Windows Vista (32-bit and 64-bit)
Microsoft Windows Server 2008 (32-bit and 64-bit)
Microsoft Windows 7 (32-bit and 64-bit)
Microsoft Windows Server 2012
Microsoft Windows Server 2012 R2
Microsoft Windows 8 (32-bit and 64-bit)
Microsoft Windows 8.1 (32-bit and 64-bit)
Microsoft Windows 10 (32-bit and 64-bit)
Microsoft Windows Server 2016
Adobe Acrobat Reader 7.0 or later (for viewing the Installation Guide)
Microsoft Internet Explorer 6.0 or later
|Database Server||SAP ASE 15.0.2, 15.0.3, 15.5, 15.7, 16|
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 or multi-byte 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.
The Quest SQL Optimizer for SAP ASE release package contains the following products:
Quest SQL Optimizer for SAP ASE 3.8.0
Refer to Quest SQL Optimizer for SAP ASE Installation Guide for installation instructions.