Unsupported trace flags

Trace flags influence Adaptive Server behavior or correct issues. However, some trace flags display unexpected behavior, and all trace flags require caution. Many trace flags are specific to Adaptive Server release 12.5.x and are not necessary for Adaptive Server 15.0. Table 4-1 describes some of the commonly used trace flags and their relevance to Adaptive Server 15.0. Before you discontinue using a trace flag, check with Sybase Technical Support, because the trace flag may be used for purposes other than those listed here.

**Table 4-1: Commonly used trace flags**
Trace flag	Description	In 12.5.x?	In 15.0?	Additional remarks
291	When enabled, predicates using the form `col1 <relop> fn(col2)`—where the datatype of col2 is listed higher than that of col1—cast the expression `f(col2)` to the datatype of the lower type (in this case, col1).	Yes	No	Functionality included in Adaptive Server 15.0
333	Disables min-max optimization.	Yes	No	No longer supported
364	Uses range density instead of total density.	Yes	No	No longer supported
370	Uses min-max index as an alternative to the table scan for single-table queries. Does not perform aggregation optimization for joins.	Yes	No	No longer supported
396	Uses min-max optimization for single-table queries.	Yes	No	No longer supported
526	Prints semi-graphical execution operator tree when showplan is enabled.	No	Yes	Functionality included in Adaptive Server 15.0

If you are running with a trace flag not listed here, contact Technical Support for assistance.

Adaptive Server 15.0 discontinues the 300 series diagnostic trace flags (302, 305, 308, 310, 311, and so on), and these will be deprecated in a future release. They are replaced with showplan options, which provide better diagnostic and more readable output.

For information about tools for investigating optimizer decisions, see Query Processing in Adaptive Server.