Hi,

I usually go the other way around – I request the collation required by K2 (Latin1_General_CI_AS) for the SQL instance, which is also acceptable for SharePoint. I have never created a clean K2 database manually.
Don't waste time, install a new SQL instance with collation for K2, migrate the SP databases to it, and install K2 alongside them.

Hi

Thank you for your response. Unfortunately, SharePoint has already been in place for some time. So it's actually K2 that needs to be added to the existing SharePoint instance.
If I understand correctly, I now have to enforce the creation of a new instance exclusively for K2??

Hi,

Well, if the K2 database is to be hosted on a supported SQL instance, then I would say that you have no other option than to request a new separate SQL instance with the required collation.

Changing the collation on the existing SQL instance for SharePoint is simply not possible.

It would be easier and safer to request a new SQL instance with the collation required by K2 and use PowerShell and the dbatools module to migrate SharePoint logins and databases between SQL instances, then just change the SQL alias on the SharePoint servers, if it is used there, and everything will continue to work. The old SQL instance can be uninstalled.

Good luck