Add a database collation checker on the initial setup.

We notice that a lot of our customer have troubles upgrading Confluence when their collation (MSSQL) or charter encoding /Colation/Engine (mysql).

Because of that they end up creating support cases to address this miss behaviours during the upgrade.

We indeed added a collation checker for both MySQL and MSSQL but what we would like is to add that check in the initial setup as well, so we will get new users unable to setup Confluence due the above error (L3/L4) instead of clients with odd errors or production outages due the wrong collation in an failed upgrade attempt (L1/L2).

Fix those settings is stressful to our customers since they only find this out months after installing Confluence (during an upgrade) and most of them do not have an allocated DBA to address these problems.

Work Around:

In case you already have a Confluence installed check the set of steps on below KB to fix the database inconsistencies:

https://confluence.atlassian.com/display/CONFKB/How+to+fix+the+collation+and+character+set+of+a+Microsoft+SQL+Server+database