No Deadlocks...Lock file locks

No Deadlocks...Lock file locks

Post by Bucke » Sat, 15 Feb 2003 00:36:37



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

 
 
 

No Deadlocks...Lock file locks

Post by Kalen Delane » Sat, 15 Feb 2003 00:15:19


On a busy system, it is not uncommon to be unable to view Current Activity.
This GUI screen takes a lot of resources. You can get almost the same
information by running sp_who2.

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


 
 
 

1. No DeadLocks ...Lock file locks

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

2. Filegroups

3. Deadlock in Index (where index is B+ tree) Locking with Intention Locks

4. Oracle Java Interfaces?

5. Kernel locks or file locks?

6. Text box, how to cancel its popup menu??? Who knows how to...

7. Has anyone seen this: deadlocks, escalation of locks

8. Powerbuilder, SQL Server(NTAS), Oracle 7.0 (NLM)

9. frequent deadlocks and lock timeout on MS SQL SERVER

10. DEADLOCKS - LOCK HINTS

11. Deadlock Checker doesn't see foreign-key locks

12. Profiler: Mode and IndexID on event class Lock:Deadlock Chain

13. Ora 04020 - deadlock detected while trying to lock object