Installing TRIRIGA 3.4.2 on Microsoft SQL Server database


Disclaimer: TRIRIGA encourages using the latest platform release when installing new TRIRIGA databases. This ensures that you have the latest platform with fixes to known issues. However, if you need to stay at 3.4.2.x and are installing on Microsoft SQL Server, review the following as you might encounter collation issues.

New database install, single-byte

There is a known issue with a TRIRIGA 3.4.2 and SQL Server new install where the single-byte option is ignored during the installation process and the resulting TRIRIGA database will be MBCS with a Latin1_General_CS_AS collation. If a single-byte environment is absolutely necessary, we suggest using TRIRIGA 3.5 where the issue has been resolved.

New database install, multibyte, non-English collation

There is a known issue with a TRIRIGA 3.4.2 and SQL Server new install where the multibyte option is selected with a collation other than English/Latin1_General_CS_AS. The chosen collation is used when building and populating the database, but the ENVIRONMENT_PROPERTIES value for “db.mbcs.mssql.collation” is not set correctly and can cause issues when new text fields and new business objects are created and populated. You can possibly get a collation conflict exception. (Note that for English collation, there is no issue since the “db.mbcs.mssql.collation” is set correctly.) We suggest you make the following changes to ENVIRONMENT_PROPERTIES…

[Admin: This post is related to the 06.29.16 post about installing TRIRIGA 3.4.2 or 3.5.0 on a non-US English database.]

Continue reading

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s