READ_COMMITTED_SNAPSHOT

  • Hi,

    Anyone out there use READ_COMMITTED_SNAPSHOT?  We have a multi-terabyte db that occasionally has locking issues generally due to badly written EF queries that I hunt down and have developers fix.  READ_COMMITTED_SNAPSHOT has been floated several times as a fix.

    I'm ambivalent about it.

    Thanks for any feedback.

    Steve

  • In my company we use it extensively and it is the default when creating any new database.

    2 Core databases
    - CRM - 3TB in size - 500 active users at all times
    - Admin system - 100GB size - 300 active users at all times

    Both systems were developed taking in consideration the issues that RCSI brings to the table - CRM uses sp_getapplock for some of its code, the other uses in-house atomic transactions processing that deal with the issue, including transaction retry in case of failure on a single thread mode.

    Most of the locking occurs during night batch processing which due to multi-threading get the number of concurrent transactions quite high (30K per minute at times) - but we are talking on the order of 20-50 dead locks per batch run on millions of transactions per batch

    And a large number of smaller db's in terms of users. All have RCSI enabled.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply