Posted by Gang He [MSFT] on 06/10/05 01:04

The second process accessing the table is blocked on X locks held by the
forst process doing the insert. These can be row, page or table locks.
read uncommitted isolation doesn't take effect for modification like
insert/delete/update. You will have to make the second process to access
the table under read uncommitted so that it doesn't not take any lock, thus
not to be blocked by the insert.

--
Gang He
Software Design Engineer
Microsoft SQL Server Storage Engine

This posting is provided "AS IS" with no warranties, and confers no rights.
<mahajan.sanjeev@gmail.com> wrote in message
news:1117740482.583193.3520@g49g2000cwa.googlegroups.com...
> Hi All,
>
> I am using a SQLTransaction to insert records into a table. At one
> time, there are 5000 or more records to be inserted one by one. It
> takes some 20-25 mins for the entire process to run.
>
> Another application accesses the same table.
>
> As long as the insert process within the transaction isn't completed,
> the second application is not getting any response from the server. I
> even tried to run a SELECT on the table in SQL Query Analyzer while the
> insert process was running and it also did not respond till the time
> the insert process finished!
>
> Is this normal that a transaction is locking up a table? How do I
> overcome it? I am using IsolationLevel.ReadUncommitted for the
> transaction.
>
> If I do not run the process within a SQLTransaction, the second process
> or running the SELECT in Query Analyzer does not hang.
>
> Thanks,
> Sanjeev Mahajan
>

[Back to original message]