Post reply

Reports blocking updates

  • July 7, 2010 at 7:00 am

    #222908

    We are using Crystal Reports and some reports take 3-4 minutes to run and what happens is a shared lock is put on the tables, the updates are having to wait until the shared lock is released. 9/10 I end up killing the report.

    Does anyone know how to not add the shared lock using isolation ?

  • July 7, 2010 at 3:58 pm

    #1189904

    If (and only IF) you are not concerned with dirty reads in your reports you could use nolock (equivalent to the read uncommitted isolation level).

    SQL 2005 also introduced optimistic isolation levels where readers don't block writers and vice versa, see

    http://msdn.microsoft.com/en-us/library/tcbchxcb(VS.80).aspx

    setting that is at the database level though so would need careful testing

    ---------------------------------------------------------------------

  • July 7, 2010 at 5:21 pm

    #1189925

    The no-locks are not doing anything. I found that there is a global isolation registry key I can set in version 8.5 it was uncommitted and version 9 committed so you can set this back.

    Thanks.

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

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