Category Archives: Lock/Blocking

Day 25 Optimization

Locking is depends upon Isolation level and Storage Engine. MySQL uses table level locking (instead of page, row, or column locking) for all storage engines except InnoDB, which uses row level locking locking system in MySQL: Implicit Locking: To maintain the … Continue reading

Posted in DeadLock, Lock/Blocking, MySQL, Others, Performance Tuning, What I learned today | Tagged , , , | Leave a comment

TempDB Contention 2.1.%

Problem: When you are performing many DML operations and makes tempdb contesnion on it, You may get wait_resource of  2.1.103 check perfomance counter: Temp Tables Creation Rate Temp Tables For Destruction When you are performing many DML operations and makes … Continue reading

Posted in DB Design, DMV, Internal, Lock/Blocking, Performance Tuning, TempDB, Troubleshooting | Leave a comment

spid in Killed/Rollback cannot kill – external

We come across a situation where we have to kill one spid which was running for quite some time, so we though killing will help us, but after killing found that that spid is not killed but stuck in our … Continue reading

Posted in Add/remove, Lock/Blocking, Others | Tagged , , | Leave a comment

Performance Tunning Part 2

After checking on the net found that there are lots of lots of good stuff (queries) already describe the performance related information, so I would like the share and refer some of the very good site. I have already blog … Continue reading

Posted in DMV, Lock/Blocking, Performance Tuning, Whitepapers | Tagged , , | Leave a comment

Lock Info

Lock: As we have discussed about introduction locks here(in our earlier blog). Here we will discuss how to trouble shoot locking. Locking is good to maintain the consistency of our data. Means when someone is update our data no one … Continue reading

Posted in DeadLock, Lock/Blocking, Performance Tuning | Tagged | Leave a comment

NOLOCK – truth

With the NOLOCK hint (or setting the isolation level of the session to READ UNCOMMITTED) you tell SQL Server that you don’t expect consistency, so there are no guarantees. Bear in mind though that “inconsistent data” does not only mean … Continue reading

Posted in Lock/Blocking, What I learned today | Tagged , | Leave a comment

Transaction isolation level

We should be aware of some information about Isolation level. As the transaction is depends on isolation level the level. Sql server has following Isolation levels: 1. Read Uncommitted (No Lock) 2. Read Committed (Blocking) 3. Repeatable Read (Phantom) 4. Snapshot  … Continue reading

Posted in Basic, Computers and Internet, Isolation Level, Lock/Blocking | Tagged , | 7 Comments