SQL Server using wrong transaction isolation level

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

問題

You're using MS SQL Server, and a banner is displayed at the bottom of the pages inside Fisheye containing this message:

Your database current transaction isolation level may lead to performance problems. Enable READ_COMMITTED_SNAPSHOT level.

原因

The Fisheye database is not configured to use READ_COMMITTED_SNAPSHOT transaction isolation level as recommended in the Migrating to SQL Server documentation.

ソリューション

  • Stop Fisheye/Crucible
  • Connect to the Fisheye database and run this SQL query:
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

最終更新日 2018 年 11 月 2 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.