1. Home
  2. Knowledge Base
  3. On-premise/Customer-Hosted Server
  4. SQL
  5. SQL Collation Conflict When Installing EIOBoard

SQL Collation Conflict When Installing EIOBoard

When installing EIOBoard, it’s possible that you may run into a SQL error similar to this one:

“Cannot resolve collation conflict between “Latin1_General_CI_AS” and “SQL_Latin1_General_CP1_CI_AS” in CASE operator occurring in SELECT statement column 1.”

The error itself will only be found in the install logs.  It will most likely manifest itself with a failed install that will auto roll-back.


Understanding Database Collation:

Here’s a good article that explains it in simple terms:



Cause of the problem:

When EIOBoard is installed, the SQL script that creates and populates the database assumes that the database will be set to the collation of “SQL_Latin1_General_CP1_CI_AS”.  In many places (ie: hundreds) this value is hard coded in the scripts where it sets columns to use this collation. The problems stems from the database itself being set to another collation.  SQL won’t let tables and columns have a collation that is different from the database itself.

We have run into cases in the past where customers have an existing SQL Server install where the server is set to a different collation.  When an EIOBoard database is created, it assumes the collation of the server, so when the script is run, it fails.


Work Around:

For now, the best work-around is to have EIOBoard install it’s own, stand-alone instance of SQL Server Express.


Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support