SQL database collation

alex9
alex9 Member Posts: 97
edited 2013-12-12 in NAV Three Tier
What's the difference between Latin1_General_100_CS_AS and SQL_Latin1_General_CP1_CI_AS SQL databases collation regarding NAV 2013 database?
Our client wants to change collation from Latin1_General_100_CS_AS to SQL_Latin1_General_CP1_CI_AS. What are potential issues?

Comments

  • jglathe
    jglathe Member Posts: 639
    Hi alex9,

    the current collation is case sensitive, the other is not. Trying to change an existing database would involve save to fbk / create new database / restore from fbk. The possible issue is that you get now non-unique entries in a table where a text field is in the primary key (ex. T225 Post Code). Then the restore would fail. To avoid this you would need to check the data before backup and clean up, if required.

    with best regards

    Jens
  • alex9
    alex9 Member Posts: 97
    We have another client's request which is about to have SQL_Latin1_General_CP1_CI_AS collation in their NAV 2013 database. They need it to support their existing SSRS reports. Whenever they create new NAV 2013 database, they have collation Latin1_General_100_CI_AS. Is there a way to have SQL_Latin1_General_CP1_CI_AS collation in NAV 2013?

Categories