Siebel Developer's Reference > Business Component User Properties > Controlling Search and Sort >

Optimizing Sort Searches

The Sort Search Optimization user property helps a database work with a rules-based optimizer (RBO). You can set it to one of the following values:

• TRUE. Enable sort search optimization.
• FALSE. Disable sort search optimization.

The Sort Search Optimization user property chooses an index from multiple indexes. To do this, it adds a search term to the SQL statement that does not modify the search result but that provides the rules-based optimizer with more information to help it choose the correct index. The Sort Search Optimization user property sets the column in this search term to the first column of the sort specification. For example, assume a query includes the following sort:

ORDER BY
  NAME, START_DT

In this example, the Sort Search Optimization user property adds the following search term to the SQL statement:

NAME >= '\1'

where:

• '\1' represents the ASCII 0 character.

Searching for values that are greater than ASCII 0 does not remove any information from the search result, but this search term helps the optimizer to choose the most effective index. This configuration improves the query performance when the business component specifies a sort specification and if the optimizer fails to choose the correct index. This access requires Sales Rep or Organization visibility, because All or All Across Organization visibility typically overrides sort specifications.

The Sort Search Optimization user property works only with Oracle 8 databases or with Oracle 9i databases that support a rules-based optimizer. It does not work with cost-based optimizers. Siebel CRM does not support it starting with Siebel CRM release 8.x. Siebel CRM disables Sort Search Optimization for DB2. For more information about rules-based optimizers, see Oracle9i Database Performance Tuning Guide and Reference.