Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I wonder if SSE 2005 supports the READ_COMMITTED_SNAPSHOT database option. What I found is this article: Features Supported by the Editions of SQL Server 2005. It states that SSE 2005 supports Snapshot Isolation Level (Row-level Versioning), but doesn't support Database Snapshot.

Does it mean that READ_COMMITTED_SNAPSHOT is not supported? Or it is about some other database snapshot feature?

share|improve this question
up vote 3 down vote accepted

Yes from that link it supports it. A Database Snapshot is a read only "frozen in time" (when the snapshot was taken) view of data. This is a tool useful in some recovery, reporting and rollback preparation scenarios.

The isolation levels you are asking about are all covered by the line talking about Snapshot Isolation Level (Row-level Versioning).

I would question what sort of workload you are putting against SQL Server Express that needs a snapshot isolation level as there are other restrictions on SQL Server Express that tend to make it not a great fit for busier, high concurrency apps (Most notably database size and memory restrictions) but this is certainly supported from that edition features matrix you linked.

share|improve this answer
There is no big load on DB, we have a lot of locks due to specific design of application. So enabling of row versioning should help. Thanks for answer! – Gopher Mar 19 '13 at 12:28
Cool - then yes this is a good solution for you and it does work. – Mike Walsh Mar 19 '13 at 12:33
Azure uses read committed snapshot by default. I think Microsoft is trying to steer development towards using this feature as a base instead of read committed with locking. In that context, it makes sense to allow developers to use it in SQL Express, regardless of whether or not the instance will be used for production. – Jon Seigel Mar 19 '13 at 16:56
John, development platforms should be configured the same as production otherwise you'll end up with different results than production (for example no locking when locking will happen in production). – mrdenny Mar 19 '13 at 20:46
@mrdenny: Yes, obviously. I was commenting on the last paragraph of the answer, specifically "I would question what sort of workload you are putting against SQL Server Express that needs a snapshot isolation level ...". What I meant was that Microsoft is motivated to include this feature in Express. – Jon Seigel Mar 19 '13 at 22:22

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.