Does MS Sql Server INSTANCE LEVEL COLLATION And DATABASE LEVEL COLLATION Have To Match For Siebel Application? (Doc ID 2719816.1)

Last updated on NOVEMBER 24, 2022

Applies to:

Goal

This is applicable to MS Sql Server DB only.

Clarification on Database Requirements for Siebel

For Production environment databases, binary or dictionary sort orders can be used in production environment databases. Binary sort order can give improved performance. For information about production environment database restrictions, see the Certifications tab on My Oracle Support. See also Microsoft SQL Server documentation.

It is critical for customers to know whether there is a dependency on the INSTANCE LEVEL COLLATION that will cause a problem (technical, performance, upgrade, etc.).

For example, if the instance level collation and Siebel database collation are different. If the Siebel application uses temporary tables where there are comparisons between the Siebel tables and the Temporary Tables then there can be performance issues. The temporary table are placed in the TempDB database which is based on the INSTANCE LEVEL COLLATION which is set at install time. If the Siebel database and the TempDB database have different collations then performance problems can occur due to additional work to follow COLLATION PRECEDENCE and possible CONVERSION that needs to be done. The use of the system databases and the impact of the INSTANCE LEVEL COLLATION should be known by Oracle and stipulated as required or not.

Please provide clarification specifically on the following with respect to the INSTANCE LEVEL COLLATION setting:

1.  Does Siebel application have any dependency on the INSTANCE LEVEL COLLATION?

2.  Should the INSTANCE LEVEL COLLATION be set to match DATABASE LEVEL COLLATION for Siebel application?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.