K2 database collation requirement – finally we have it stated in the right place

If you read my old blog post on Installing SQL Server instance for K2 blackpearl you probably aware that K2 database requires very specific SQL Server instance collation in case you care to be in supported state. The main problem was that this requirement has been mentioned in quite obscure place which no sane person even reach in endless quest for knowledge 🙂 That original requirement location was quite close to that joke about ginormous EULA and vendor injecting a sentence which says: “If you really read through this EULA till this place please give us a call to claim your 1000$ reward”…

There is no doubts that K2 is very flexible and versatile platform but when it comes to K2 database collation you only have a Hobson’s choice. Many product vendors have similar requirements for their back-end databases and there is nothing wrong with that, but problem we had in case of K2 was that a lot of people failed to realize that only one collation is required and supported, i.e. Hobson’s choice was poorly presented to them 🙂

Finally K2 blackpearl compatibility matrix was updated this month to reflect this requirement and I really hope this will clarify K2 collation requirement once and for all. We all agree that at least compatibility matrix is something we all read before rushing into installation or upgrade, right? 😉

So navigate to K2 blackpearl Compatibility Matrix page > SQL Server section notes and… lo and behold this:

blackpearl collation requirement

I hope this will help people to avoid collation related issues from now on and we are all clear that:

Latin1_General_CI_AS collation is required on the SQL server instance hosting the K2 database

Please follow and like us:
error0

Leave a Reply

Your email address will not be published. Required fields are marked *