Post reply

SET TRANSACTION ISOLATION LEVEL

  • December 24, 2003 at 8:58 am

    #66237

    A company department uses Cognos' Impromptu to query against some of our databases for analytics. Impromptu starts by setting the transaction isolation level to read committed. Does this put restrictive locks on the tables being queried?

  • December 24, 2003 at 9:06 am

    #487770

    No. Read committed is just a little more restrictive than read uncommitted. It doesn't allow dirty reads, but it doesn't guarantee repeatable reads either. In other words, if the same select statement is issued twice within the same transaction, you migth get different results each time.

    So the data is allowed to change while this transaction is running.

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

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