ePO 5.x supports all Microsoft SQL Server collations that use the following two SQL collation properties:
- Case Insensitivity (CI)
- Full ASCII character set support - This set is included in all Unicode-based character sets.
If your SQL Server uses SQL collation that meets the above criteria, it is supported.
IMPORTANT:
- The SQL collation of the SQL Server must match the collation of the ePO database.
- Changing the collation of the ePO SQL database itself is not supported. If an SQL collation mismatch occurs, either:
- Change the collation of the SQL Server itself
Or
- Move the ePO SQL database to an instance that matches the database collation.
- ePO is primarily tested with SQL_Latin1_General_CP1_CI_AS, which is the default for English United States. Test striping is performed against some of the default SQL collations for non-English languages.
Use SQL to make sure that the collations match and sync with the
ePO_DB and ePO_Events databases.
Make sure that the Server Collation matches the ePO core Database collation,
and that it is a supported collation.
To determine if the SQL Server has the correct collation:
- Click Start, Programs, Microsoft SQL Server, Query Analyzer.
- Connect to the SQL Server.
- Open a query window, and select the ePO database. For help, see KB67591 - How to run a SQL script provided by Technical Support against the ePO database.
- Copy the following queries, and paste them into the Query window:
SELECT CONVERT (varchar, SERVERPROPERTY('collation')) AS 'SQL Server Instance Collation';
SELECT name AS 'EPO Database', collation_name FROM sys.databases WHERE name = N'<Enter EPO_DB_Name Here>';
NOTE: The following query is for ePO 5.10 versions only. In addition, verify that the EPO Events Database collation is correct:
SELECT name AS 'EPO Events DB', collation_name FROM sys.databases WHERE name = N'<Enter EPO_Events_DB_Name Here>';
5. Click
Execute Query.