New Alert published about Siebel repository migrations from binary sort collation to CI (case insens
Hi,
When you are implementing Siebel CRM using a CI (Case Insensitive) collation in the target, Siebel test- production or production databases and your development Siebel repository is available to the Siebel CRM development environment installed as binary sort order, your source repository (dev) on the binary sort order system may include data that is unique only due to a case or accent differences.
In such cases, when the repository is migrated from dev to test (or prod) unique key violation errors may be filed for the Siebel repository import process.
The new Siebel CRM production upgrade process may fail when using a Case Insensitive Collation on a Microsoft SQL Server Database [ID 1451289.1]
When you are implementing Siebel CRM using a CI (Case Insensitive) collation in the target, Siebel test- production or production databases and your development Siebel repository is available to the Siebel CRM development environment installed as binary sort order, your source repository (dev) on the binary sort order system may include data that is unique only due to a case or accent differences.
In such cases, when the repository is migrated from dev to test (or prod) unique key violation errors may be filed for the Siebel repository import process.
The new Siebel CRM production upgrade process may fail when using a Case Insensitive Collation on a Microsoft SQL Server Database [ID 1451289.1]
0