SQL Server using wrong transaction isolation level
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
Problem
You're using MS SQL Server, and a banner is displayed at the bottom of the pages inside Fisheye containing this message:
1
Your database current transaction isolation level may lead to performance problems. Enable READ_COMMITTED_SNAPSHOT level.
Cause
The Fisheye database is not configured to use READ_COMMITTED_SNAPSHOT transaction isolation level as recommended in the Migrating to SQL Server documentation.
Resolution
Stop Fisheye/Crucible
Connect to the Fisheye database and run this SQL query:
1
ALTER DATABASE <db_name> SET READ_COMMITTED_SNAPSHOT ON;Please change <db_name> accordingly in the query above.
This query will wait until all active connections to the database are closed. Other active connections will block the query from running.
Start Fisheye/Crucible
Was this helpful?