IQDoc
ITIQPro Docs Maintenance Connection Everywhere (MCe) · EAM/CMMS manuals
PM Collation - you 'need' a different collation
An on-prem, your own servers, issue

This document is answering the question from an On-Prem customer:

>We can't change the SQL server collation as it will affect other running databases.

So that means that you are unable to realistically long term run on-prem with Accruent MC.

So what to do?

Your status:

Accruent MC REQUIRES that you have the SQL_Latin1_General_CP1_CI_AS collation. See also MC 2025 upgrade pre-requisites

It means you have ANOTHER vendor/database that REQUIRES that you have a DIFFERENT collation.

And likely at points, the 2 (or more) vendors will require different versions and/or editions of MS SQL Server.

It is NORMAL when running on-prem to have to change setup due to conflicts between the requirements of different applications you are hosting. It's part of what you take on when you decide to run on your own equipment instead of our SaaSs.

While we may have created temporary fixes that fix specific problems to allow you to run with the wrong collation, these are temporary fixes not real 'solutions'.

Your real options are:

  • Install a supported version of MS SQL Server with the required collation. This obviously will cause problems for your other applications.
  • Install a SECOND MS SQL Server with the Accruent requirements. This is the normal solution for on-prem with different requirements such as approved versions and collation. For example upgrading to MC 2025 requires you have EXACTLY MS SQL 2019, and then after you upgrade you can upgrade MS SQL to the recommended 2022.
  • Move to one of our SaaSs. We obviously run them with MS SQL Server set up correctly and, as Accruent's requirements change, we change so you don't have to worry about it.
  • As there are collation issues, such as with PMs, move that functionality to MCe. MCe does not have any requirements for a specific collation, and we are committed to that in the future as well.

On prem responsibilities:

Please understand: When you run your own servers, you are REQUIRED to make changes as each of your venders, not just Accruent or us, has new requirements. Choosing On-Prem should never be to save money - doing it properly has benefits for some customers, but saving money is extremely unlikely after all costs including your equipment and licensing and Professional services are added up. Back in 2003 - ok, on-prem sometimes saved money. But in modern days, it is very unlikely.

It's not a bug, it's not covered by SMA

Note this is NOT considered a bug in Accruent MC. Every vendor has their requirements, and those requirements change from version to version. In general your choice are:

  • run meeting the current requirements
  • don't upgrade (which obviously has it's own set of, likely different, issues.)
  • run on SaaS