|
|
|
|
|
| |
To implement secure concurrent access, database systems such as SQL Server
implement a complex locking mechanism. Monitoring SQL Server locks for blocking
can be critical to efficient use of databases.
If not checked & resolved quickly, "blocking" as it's known can be very serious
& can soon bring any system relying on the underlying data to it's knees.
|
|
|
 |
Windows applications often use SQL Server as their database of choice. SQL
server is a relational database like many others, holding its data in a series
of tables, with indexes & keys helping to provide fast, efficient access.
To help maintain secure & concurrent access, database systems such as SQL Server
use a complex locking mechanism.
Whilst this is extremely efficient at
protecting data and ensuring changes are applied in the correct sequence etc.,
it can mean that one user or process can easily prevent another from continuing
simply because it has locked a resource the other needs.
|
|
|
In well designed, efficient databases, locking problems should be kept to a minimum. Inevitably,
some contention problems will occur from time to time but they should be so
quick that the end user wouldn't notice. However, in poorly designed,
overstretched or poorly performing systems blocking can be an extremely
important factor, in terms of speed & data delivery for all connected
users. Locking errors can also cause other secondary errors, such as the
transaction log file to grow excessively and even fill up, so it is extremely
important to detect issues early, before the problem gets out of hand.
|
|
|
|
|
|
An example of how Process A is preventing
(blocking) Process B from continuing |
|
|
SQL Server lock monitoring would be of benefit with any business critical
system, application or web site that relies on a SQL Server database for its
data store.
|
|
|
It is available either individually or as part of a
Quick Monitor solution. Specifically it is available ...
|
|
|
|
|
|
|
|
|
|
|
|
|