When using oledb connection to SQL Server (XI R2) and a modified oledb.sbo parameter file BO still acts with isolation level 'read committed'. The sbo file has been modified by adding the following line in the SQL Server 2005 section of the file : u2018<Parameter Name="Transaction Isolation Level">READ UNCOMMITTED</Parameter>. This extra line does not result in a different isolation level being used. Other suggestions I found reflect the modification of the ConnectInit parameter in the connection definition. Apparently this requires a stored procedure ?.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.