---
title: Snapshot isolation for high-volume transactions
description: Because deadlocks can occur in some tables in high-concurrency environments with contention for shared data, you can enable READ_COMMITTED_SNAPSHOT in SQL Server to improve the performance and scalability of applications with long-running transactions.
component: pingfederate
version: 13.1
page_id: pingfederate:performance_tuning_guide:pf_snapshot_isolation
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/performance_tuning_guide/pf_snapshot_isolation.html
llms_txt: https://docs.pingidentity.com/pingfederate/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: April 11, 2023
---

# Snapshot isolation for high-volume transactions

Because deadlocks can occur in some tables in high-concurrency environments with contention for shared data, you can enable READ\_COMMITTED\_SNAPSHOT in SQL Server to improve the performance and scalability of applications with long-running transactions.

When snapshot isolation is enabled, each transaction reads data from a snapshot of the database taken at the start of the transaction rather than directly from the database itself.

Because there can be some overhead with snapshot isolation, evaluate and test this setting carefully before deploying in production environments. For more information on snapshot isolation and how to configure the option, see [Snapshot Isolation in SQL Server](https://learn.microsoft.com/en-us/dotnet/framework/data/adonet/sql/snapshot-isolation-in-sql-server) in the Microsoft documentation.