ISOLATION LEVEL READ UNCOMMITTED

• PK-256781

  Old Hand

  Points: 382

  More actions

  September 28, 2005 at 11:33 am

  #91442

  Hi,

  I have an overnight process that runs hundreds of sprocs.  Prior to that some data imports run using DTS.

  In one of the sprocs I check for the existence of recs and based on the records existing, the code takes a certain path.

  The issue is the code always thinks that no recs exist.  When the proc is run in isolation the following morning it identifies that records exist and the code execution follows the expected path.

  I have logged some debugging data that tells me the check for the existence of the recs occurs 5 minutes after records have been created that satisfy my check.

  The sproc includes the following:

  SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED

  I am wondering could this be causing the problem?  Although the records have been written to the database by the DTS, could the sproc not be getting the latest version of the data because of the isolation level?

  Regards,

  PK

• Ninja's_RGR'us

  SSC Guru

  Points: 294069

  More actions

  September 28, 2005 at 11:41 am

  #593769

  Actually it means that the server will read ALL data, committed or not (read even if the commit transaction hasn't been issued).

  So I would doubt that this is the problem...