Very Computer

Any thoughts on this.?

Plus one other question:
A developer in one transaction does the following

Insert record
read same record
update the record
commit

Isn't it better to Insert record commit, read record, update record commit?

Just wondering

Jim

Deadlocks would rarely be the cause of your problems with Current Activity
window. Deadlocks are automatically resolved by SQL Server, usually very
quickly. If you have a reaon to suspect lots of deadlocks in your
applications, you should also make sure you are trapping them in your
applications and resubmitting the transactions.

Whether or not you want to commit your transaction after the insert depends
on whether you want to be guaranteed that your new row won't change before
you can read and update. What are your transactional needs?

HTH

--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com

Quote:> What would be the cause of the Management->Current Activity file being
> locked,
> yet when you run traces with 1204, 1205, 3605 you don't see any dead
locks.
> Just thousands of reads over a 15 min period?

> Any thoughts on this.?

> Plus one other question:
> A developer in one transaction does the following

> Insert record
> read same record
> update the record
> commit

> Isn't it better to Insert record commit, read record, update record
commit?

> Just wondering

> Jim