Symptoms

K2 officially supports only one specific collation for K2 database and SQL Server instance which hosts K2 database: Latin1_General_CI_AS What are the options to convert your existing database to supported collation?
 

Diagnoses

Upcoming 4.7 release will require you to perform K2 data base consolidation and it is good time to check on your K2 databases, including what collation do you have on them at the moment. Unfortunately at the moment there is no official tool which will perform K2 database conversion from unsupported collation to supported one.

In the process of K2 database consolidation you may create new SQL instance for consolidated K2 database in supported collation and Consolidation Tool will create consolidated DB for you in supported collation. But this is not officially supported scenario and neither this scenario was tested by K2. K2 database collation requirement (which you may find stated in K2 blackpearl compatibility matrix in Notes under SQL Server section) is in place because all testing is performed only on this collation consequently only this one is fully supported. Other collations will work but in case you want to run fully supported and tested configuration you have to use required collation - Latin1_General_CI_AS.

There are plans to introduce changes to K2 setup manager to flag a warning when you trying to create K2 database on an instance with wrong collation or force supported collation in some other way. For supported way of conversion of existing K2 DB to supported collation there is a plan to publish KB article with the appropriate steps to convert the collation via SQL scripts.
 

Resolution

At the moment K2 does not provide tools or instructions to perform conversion of your existing K2 DB to supported collation. You have to make sure that K2 DB provisioned with correct collation from the very beginning (installation stage) or work with experienced SQL DBA which can assist you with conversion of K2 DB to supported collation by means of SQL scripts.