In SQL Server, collations dictate the sorting rules, case sensitivity, and accent sensitivity properties for your data types such as char and varchar. They determine the code page and corresponding characters that can be represented for those data types. “In this article, we will discuss this error message “Change Database Collation: EPO core collation is {core_collation}, and ePO events DB and SQL server should match with ePO core collation”. Please see Trellix ePolicy Orchestrator Installation on Windows Server.
Trellix ePO on-premise software supports all Microsoft SQL Server collations using the following two SQL collation properties:
– Case Insensitivity (CI)
– Full ASCII character set support (these characters are included in all Unicode-based character sets)
Understanding the locale requirements, sorting order, and case and accent sensitivity of the data you’re working with is crucial whether you’re installing a new instance of SQL Server, restoring a database backup, or connecting server to client databases. To list the collations that are available on your instance of SQL Server, see sys.fn_helpcollations (Transact-SQL).
When you select a collation for your server, database, column, or expression, you’re assigning certain characteristics to your data. These characteristics affect the results of many operations in the database.
Also, see how to Disable SQL Auto Close: Auto Close is enabled for both ePO and ePO Events Databases, how to Migrate Veeam MSSQL Database to a new MSSQL Server, and apply Fixes to Trellix ePolicy Orchestrator Installation Errors.
Is this truly an error “ePO events DB and SQL server should match with ePO core collation”?
To understand this error message below. Let’s review some fundamentals. Microsoft recommends that the collations of user-defined databases must match the collation of master or model. Else, collation conflicts can occur that might prevent code from executing.
With this in mind, Trellix emphatically stressed that “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, do either of the following
- Change the collation of the SQL Server itself is possible. But might end up as a tricky operation you may not want to embark upon.
- Move the ePO SQL database to an instance that matches the database collation.
Note: I will not do anything as this is not an issue for Trellix as stated in their product documentation and I quote.
IMPORTANT: 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’s a supported collation.
I confirmed that SQL server collation matched with the ePO_Db and the ePO_Events. Therefore this task is marked completed. Here is how to how to upgrade Trellix ePolicy Orchestrator.
Change Database Collation
Note: I repeat, when this error is prompted and you have seen a mismatch between the SQL Server collation and that of the ePO databases. Then you can perform the following below to change the ePO database collation to the SQL server collation.
But if you wish to learn how to change database instance collation, please follow the steps below.
Launch SQL Server Management Studio as shown below,
In Object Explorer, connect to an instance of the SQL Server Database Engine.
Right-click the database that you want and select Properties.
Select the Options page, and select a collation from the Collation drop-down list.
Note: I did not change this but only showing you how to change from one collation to another.
After you are finished, select OK.
As I said before, you do not need to change to this collation if there is no mismatch. ePO is primarily tested by Trellix with SQL_Latin1_General_CP1_CI_AS, which is the default for English United States. But they support all collations with certain requirements as mentioned above.
Bonus Tips
The nested triggers option controls whether an AFTER trigger can cascade. That is, perform an action that initiates another trigger, which initiates another trigger, and so on.
See How to Fix Microsoft Outlook Not Syncing Issue, how to Configure SQL Server Instance to listen on a specific TCP Port, and how to upgrade Microsoft SQL Server 2019 to 2022
Configure Nested Triggers option
After launching the explorer, Right-click the SQL Server that you want and select Properties. Select Advanced and set the “Allow Triggers to Fire Other” to “True”.
I hope you found this article useful on “Change Database Collation: EPO core collation is {core_collation}, and ePO events DB and SQL server should match with ePO core collation”. Please feel free to leave a comment below.
