SQLServer DB is using a collation which is not case sensitive
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
When trying to migrate the HSQLDB to SQL Server the following message can be seen on the page:
1
The database is not using case-sensitive Unicode. FishEye and Crucible require that the database is case-sensitive and uses a UTF8 encoding to support internalization., or before Fisheye 3.10
1
The database is not using Unicode. FishEye and Crucible require that the database uses a UTF8 encoding to support internalization.From the logs:
1
2012-07-26 10:22:31,599 ERROR [btpool0-83 ] fisheye.app DBType-isSqlServerCollationCaseSensitive - SQLServer DB is using a collation which is not case sensitive: 'SQL_Latin1_General_CP1_CI_AS'Diagnosis
Run the following query to verify the default collation:
1
SELECT SERVERPROPERTY('Collation');Cause
The incorrect default collation is being used by the SQL Server.
Solution
Resolution
Changing the default collation for the SQL Server might impact the other databases running on it. Proceed with care and backup all data before applying any changes.
Shutdown Fisheye.
Set the default database collation in SQL Server to
Latin1_General_CS_ASas indicated in our documentation.Start Fisheye.
Was this helpful?