Post reply

Isolation Level

  • August 21, 2012 at 6:53 pm

    #260324

    Ok so here is the situation. I have a database that has a crappy front end application that connections in via a generic sql logon. Not my design. Any how the application causes blocking at an alarming rate and after some testing if I can set the Isolation Level to 'READ UNCOMMITTED' that then this app runs it will be ok. It just a small thing checking session states and there are only 6 tables in there with the locks always on the same table.

    Is this possible or are there any better ideas ?

    Thanks

    Hope this helps...

    Ford Fairlane
    Rock and Roll Detective

  • August 22, 2012 at 1:37 am

    #1528474

    Many better options.

    Read uncommitted is the same as nolock, allows for dirty reads, dupliate reads, missed reads. See - http://blogs.msdn.com/b/davidlean/archive/2009/04/06/sql-server-nolock-hint-other-poor-ideas.aspx

    What would probably be a better approach would be to consider one of the snapshot isolation levels (read committed snapshot or snapshot) if tuning the code isn't an option or doesn't help enough. See if they will fix the problem

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • August 22, 2012 at 1:51 am

    #1528481

    Hi Gail,

    Thanks for that. I will give shot and see what happens.

    Hope this helps...

    Ford Fairlane
    Rock and Roll Detective

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

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