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.

Workaround:

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 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.

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."

Workaround:

You must uninstall the previous version of SQL Optimizer, and then install the current version again.

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

Workaround:

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.

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.