Re: ADO.NET Transaction Locking
- From: "Marina Levit [MVP]" <someone@xxxxxxxxxx>
- Date: Wed, 19 Apr 2006 14:11:58 -0400
Usually, this works fine without anything special. I don't understand why if
the entire transaction takes 2 seconds, why other clients are timing out,
even if the transaction is locking the whole table? That should be quick
enough, so that the other clients can just wait the 2 seconds, and then the
data they want should be available again.
In general, make sure your updates and anything your stored procedure is
doing, is using the table index for its queries, so table scans aren't being
done.
"scott" <scott@xxxxxxxxxxxxx> wrote in message
news:2F64AACF-34DE-41EA-8987-70FF2A5905F2@xxxxxxxxxxxxxxxx
I have a transaction that is Updating or inserting multiple tables(12 or
more) This transaction takes about a 2 seconds to perform. During that
two
seconds. We are getting timeouts expired errors from other clients
requesting records from the same 12 or so tables. What setting is there
to
say only lock the changed or new records do not lock the entire table
which
is what appears to be happening?
I am using SPs to do all inserting and a multiple command objects.
What is occuring in the ado.net lock is it a table lock page lock or
record
lock.
These are simple insert or updates, except for one procedure that
validates
the data.
.
- Prev by Date: Re: Create my own db connection wizard
- Next by Date: How to select on datatable to exclude objects
- Previous by thread: DataRelations
- Next by thread: Re: ADO.NET Transaction Locking
- Index(es):
Relevant Pages
|
