Siebel Database Upgrade Guide > Siebel Database Upgrade Planning >

About Database Sort Order in the Siebel Environment

Environments: Development, production test, production.

Sort order (also called collation sequence) is specified during the initial installation of a database and defines the way in which the database sorts character data when executing queries. Sort order support depends on both the code page of the database and whether it is used in a development or a production environment:

• Development environments. For development databases, you must use a binary sort order due to the functional limitations of databases that use a nonbinary sort order.
• Production environments. For production databases, it is strongly recommended that you use binary sort order to prevent possible performance degradation.

The settings for binary sort order are unique for each database platform. For Siebel language support, Unicode support, and legacy code page support, see 1513102.1 (Article ID) on My Oracle Support.

Sort Order Considerations for Siebel Databases

If your deployment requires that you use a nonbinary sort order (for example, if your local language does not use binary sort order), then you must consider several functional limitations that particularly affect development environment upgrades. If these limitations are unacceptable, then consider re-creating your database to use binary sort order. However, be aware of these considerations:

• You cannot use Siebel Tools to generate a Siebel Repository file (SRF) on a database that uses a nonbinary sort order.
• You cannot perform a repository merge on a database that uses a nonbinary sort order.
• Databases that use nonbinary sort order might perform slower than databases that use binary sort order.

For Siebel language support, Unicode support, and legacy code page support, see 1513102.1 (Article ID) on My Oracle Support.