IsolationLevel of Transaction - please help

[Tilfried Weissenberger]

Hi,

sorry for asking this maybe simple question. All I want is to know
which type of transaction isolation level I need to specify to be able
to revert multiple SQL commands, WITHOUT blocking the entire table!

Currently, when specifying no level, the complete table is locked
until the transaction is commited. As I have many concurrent
transactions on different rows in the same tables this is not a very
efficient way.

If anyone knows what the different (meaningless to me)
System.Data.IsolationLevel Enum values do/mean, I'm glad to get
enlighted!

thanks!

regards, Tilli

 

[Hector Correa]

Try with READ COMMITTED.

Here is a brief description on what each level means/does:

* SERIALIZABLE: No other transaction can UPDATE or INSERT
records to table.
* REPEATABLE READ: No other transaction can UPDATE
records retrieved in SELECT statements. Other
transactions can INSERT new rows, though.
* READ COMMITTED (default): Other transaction can UPDATE
records retrieved in SELECT statment.
* READ UNCOMMITTED: Selects can read dirty records.

 

[Tilli]

Hi Hector,

thanks a mil - sure makes life easier to know the difference.

regards, Tilli