Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Mohamed Sajjad (Mohamed Sajjad)
LTI

LTI
IN
Mohamed Sajjad Member since 2016 8 posts
LTI
Posted: Oct 3, 2019
Last activity: Oct 4, 2019
Posted: 3 Oct 2019 0:58 EDT
Last activity: 4 Oct 2019 12:40 EDT
Closed

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***

To see attachments, please log in.
System Administration
Support Case Exists

Posted: 5 years ago
Posted: 4 Oct 2019 12:40 EDT
Jie Long (LONGJ)
PEGA
Fellow, Software Architect, Services Engineering
Pegasystems Inc.
US

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. 

https://www.olcot.co.uk/revised-difference-between-collation-sql_latin1_general_cp1_ci_as-and-latin1_general_ci_as/ 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice