TL;DR

You have to have the required collation for the server, ent database(s) and reg database if you are using MC to any great degree.

If you are using/are willing to use MCe for any places you run into problems while running, then we have a fix that works for the MC 2025 upgrad.

Details

The MC 2025 upgrade has in the release we are using two Collation error bugs. The APS/MCC/ITIQPro upgrade package has fixes for them.

We had previously (2025 or 2024) supplied Accruent with a fix and they applied the fix in their MC 2025 upgrade for that specific location.

In 'our' MC 2025 upgrade we have fixed it broader than just that one location, so customers of ours shouldn't have a problem with this during the upgrade.

We have more testing to do as upgrades come out over the next few years, but we have a concern that as Accruent is moving to using temp tables, and they are currently ignoring at least some collation issues, this may require that you use MCe Admin1/WO4/WO7 for any areas that MC has collation bugs, or the db server must be set to the USA collation and our 'fixes' may be a patch on the 'first' issues, not a solution. Stay tuned. If you want to be notified of updates, send a message to support@maintenanceconnection.ca to be put on a notification list.

During the upgrade, we see that Accruent has done more that requires the correct collation in the server (creating temp tables/sps), and while we fixed it in the upgrade, there may be more.

We have reports from at least one question that having the wrong collation causes PMs to fail.