Share via

Enabling RCSI and ADR on SSISDB and ReportServer

Louis Davidson 21 Reputation points
2026-02-24T22:16:48.07+00:00

We're considering enabling two database-level settings on SSISDB and ReportServer:

  • READ_COMMITTED_SNAPSHOT (is_read_committed_snapshot_on = 1) — reduces blocking by using row versioning instead of shared locks
  • ACCELERATED_DATABASE_RECOVERY (accelerated_database_recovery_on = 1) — speeds up recovery and enables instant rollback using a persistent version store

Both are generally considered safe for most workloads, but wanted to check before making the change. Has anyone run into issues with either of these on SSISDB or Report Server specifically? Any concerns or reasons we shouldn't enable them?

I will be doing this on SQL Server 2022, just for metadata queries, so they don't block anyone.

SQL Server Integration Services
Answer accepted by question author
  1. Erland Sommarskog 133.1K Reputation points MVP Volunteer Moderator
    2026-02-26T20:04:49.13+00:00

    I spoke with my friends and one noted that SSISDB is basically a log file for SSIS, and if there is a heavy traffic, you don't want readers blocking writers. He also thought that ADR could be beneficial for SSISDB.

    For ReportServer, the comment was that the database is not busy, so he could not see that it would matter very much in any direction.

    You found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-02-24T22:16:58.03+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Enabling both READ_COMMITTED_SNAPSHOT (RCSI) and ACCELERATED_DATABASE_RECOVERY (ADR) on SSISDB and ReportServer can generally be considered safe for most workloads. Here are some key points to consider:

    1. READ_COMMITTED_SNAPSHOT (RCSI): When RCSI is enabled, it reduces blocking by using row versioning instead of shared locks. This can improve concurrency for read operations, which is particularly beneficial in environments with many simultaneous transactions.
    2. ACCELERATED_DATABASE_RECOVERY (ADR): ADR enhances recovery speed and allows for instant rollback through a persistent version store. This feature is beneficial for workloads that involve long-running transactions or significant transaction log growth.

    However, there are a couple of considerations:

    • Performance Overhead: While ADR provides benefits, it may introduce some performance overhead due to version storage and processing, especially in write-intensive workloads. It's advisable to monitor performance after enabling these features to ensure they meet your expectations.
    • Compatibility: Ensure that your specific use cases and workloads on SSISDB and ReportServer are compatible with these settings. Testing in a non-production environment before rolling out changes to production is recommended.

    Overall, if your primary goal is to reduce blocking for metadata queries and improve recovery times, enabling these settings should be beneficial. Just keep an eye on performance metrics post-implementation to address any unforeseen issues.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.