Concurrency Control

  • Can anyone guide me about how to ensure concurrency control for an inventory system ?

    Mufaddal


    Mufaddal

  • Hi there

    In general, its very important to keep transactions as short as possible, and as "focused" as possible. When I say focused, I mean as few rows/tables as possible are involved in an update/delete/insert op. Be very careful drawing out a transactions over more than a couple of seconds if the database structures are used frequently. The problems tend to stem from a bunch of (generic) routines in which a transaction is opened too early and spans for long period of time to ensure data and business process integrity. Design carefully.

    In SQL Server, writers block readers, and with a default isolation level of serialisable for com+ transactions (com v1.0, v1.5 we can control this), the risk of blocking and deadlocking issues are increased substantionally over other DBMS's.

    The links from 5409045121009 are good ones to start with.

    Cheers

    Ck

    Chris Kempster

    http://www.chriskempster.com

    Author of "SQL Server 2k for the Oracle DBA"


    Chris Kempster
    www.chriskempster.com
    Author of "SQL Server Backup, Recovery & Troubleshooting"
    Author of "SQL Server 2k for the Oracle DBA"

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

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