Event ID - 5076

Event Id5076
DescriptionWarning: Changing default collation for database %.*ls, which is used in replication. It is recommend that all replication database have the same default collation.
Event InformationCAUSE:
You have issued the ALTER DATABASE statement with the COLLATE clause to change the default collation on an existing database. The database is configured as a Publisher (sp_replicationdboption was used to set the "merge publish" and/or "publish" option to true), or the database is configured as a distribution database.
Microsoft recommends that all databases in a replication topology have the same collation to avoid potential case sensitivity, sorting, and translation issues.

The following is not a comprehensive list of all potential problems; it is a subset of the high-level types of issues you might encounter:

For example, consider the scenario where the publishing database has a case-sensitive collation, but the subscriber has a case-insensitive collation. On the publisher you have a row with the primary key equal to "Test" and a row with the primary key equal to "TEST". But if you try to replicate that data to a case-insensitive Subscriber, replication will fail with a duplicate key error. The same scenario could occur with a difference in accent sensitivity, kanatype sensitivity, or width sensitivity. Even with the same case-sensitivity and with all unicode data types, you could have different results on servers with different collations. For example, an application that returns the top 10 rows could return completely different data sets on a dictionary order collation compared with a binary order collation. Result set differences could also occur if the difference is between a sort order with uppercase preference and one without uppercase preference.

It is recommended that you use the same collation for all databases in your replication topology. If you must have different default collations for databases within the same replication toplogy, thoroughly test your specific replication scenario with realistic data, and adjust your configuration to account for any anomalies that could occur.
Reference LinksMicrosoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 5076

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.