COM+ Isolation Level and SQL Server Isolation Level

  • Hi all,

    Even if the SQL Server Isolation Level, say, Read Committed,

    when a COM+ business object is used for transaction,  the Isolation Level is changed to Serializable, why?

    Is there any workaround for that?

    Please help...

    Thanks

    Jag

  • This is a known problem of COM+.By default, it uses Serializable Isolation Level, which is the most restrictive one. This can be changed by stored procedures used in COM+ giving SET TRANSACTION ISOLATION LEVEL READ COMMITTED, or by giving appropriate hints in SQL statements

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

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