Posted: 3 Oct 2019 0:58 EDT Last activity: 4 Oct 2019 12:40 EDT
Does PEGA support Latin1_General_CI_AS
Our project use PEGA V7.3.1 and database SQL Server 2016, the current setting of collation in SQL Server instance level is Latin1_General_CI_AS, We created PEGA database under the instance with same collation Latin1_General_CI_AS, we will create user databases also with same collation Latin1_General_CI_AS.
Because Latin1_General_CI_AS isn’t Microsoft SQL Server default collation setting (Microsoft SQL Server default collation is: SQL_Latin1_General_CP1_CI_AS), we want to get confirmation from PEGA whether PEGA software support Latin1_General_CI_AS.
***Moderator Edit-Vidyaranjan: Updated SR details***
Collation is decided upon the customer's own globalization/localization requirements. The major difference between Latin1_General_CI_AS and SQL_Latin1_General_CP1_CI_AS is the character expansions. Depends on how would you require the behavior, you may choose either of them.