Transaction Isolation Level

Hello,

Is the following code handled different in .NET 1.1 and .NET 2.0?

public SqlTransaction BeginTransaction()
{
return this.BeginTransaction(IsolationLevel.Unspecified, null);
}


It seems that running this code and starting a transaction under 2.0 we run
into locking issues if more than one transaction should be opened at the
same time, while running on 1.1 there are no problems. Does it make a
different to use IsolationLevel.Unspecified there?

Any hint would be great.

Thanks!

Best Regards,
Andreas Pfanner

You'd need to open a Profiler trace to see what's going on in the
database. What operations are you performing inside of the
transaction? Perhaps explicitly specifying an isolation level would
help the server allocate resources more efficiently.

--Mary

On Tue, 29 Apr 2008 14:14:03 +0200, "Andreas Pfanner"
<andreas.pfanner@teleport.vol.at> wrote:

>Hello,
>
>Is the following code handled different in .NET 1.1 and .NET 2.0?
>
>public SqlTransaction BeginTransaction()
>{
> return this.BeginTransaction(IsolationLevel.Unspecified, null);
>}
>
>
>It seems that running this code and starting a transaction under 2.0 we run
>into locking issues if more than one transaction should be opened at the
>same time, while running on 1.1 there are no problems. Does it make a
>different to use IsolationLevel.Unspecified there?
>
>Any hint would be great.
>
>Thanks!
>
>Best Regards,
>Andreas Pfanner
>