Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 2157154 - Last Review: April 2, 2012 - Revision: 2.0
The 'Blocked Process Threshold' configuration does not work as expected for values less than 5
If you configure the 'blocked process threshold' to a value of less than 5 (but greater than 0), SQL Server will not detect any blocking problems for that value. This is because 5 is the lowest value that SQL Server can use to detect blocking problems with this feature.
The SQL Server lock monitor is responsible for implemeting the logic to detect a blocking scenario if the 'blocked process threshold' value is greater than 0. However, the lock monitor only wakes up every 5 seconds to detect this condition (it is also looking for other conditions such as deadlocks). Therefore, if you set a 'blocked process threshold' value to 1, it will not detect a process that has been blocking for 1 second. The minimum time it can detect a blocked process is 5 seconds.
For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table:
Collapse this tableExpand this table
| Rule software | Rule title | Rule description | Product versions against which the rule is evaluated |
SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA)
| Very low blocked process threshold setting detected
| The SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect a low value for 'blocked process threshold'. The SQL Server 2008 R2 BPA supports both SQL Server 2008 and SQL Server 2008 R2. If you run the BPA tool and encounter a Warning with the title of Engine -Very low blocked process threshold setting detected, then your SQL Server 2008 or SQL Server 2008 R2 installation has a 'blocked process threshold' value between 1 and 4 as found in sys.configurations (the "value_in_use"). BPA uses SMO to find the run value of this configuration. | SQL Server 2008
SQL Server 2008 R2
|
SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA)
| Very low blocked process threshold setting detected
| The SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to detect a low value for 'blocked process threshold'. If you run the BPA tool and encounter a Warning with the title of Engine -Very low blocked process threshold setting detected, then your SQL Server 2012 installation has a 'blocked process threshold' value between 1 and 4 as found in sys.configurations (the "value_in_use"). BPA uses SMO to find the run value of this configuration. | SQL Server 2012
|
APPLIES TO
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Workgroup Edition
- Microsoft SQL Server 2008 Developer
- Microsoft SQL Server 2008 Enterprise
- Microsoft SQL Server 2008 Express
- Microsoft SQL Server 2008 Express with Advanced Services
- Microsoft SQL Server 2008 R2 Datacenter
- Microsoft SQL Server 2008 R2 Developer
- Microsoft SQL Server 2008 R2 Enterprise
- Microsoft SQL Server 2008 R2 Express
- Microsoft SQL Server 2008 R2 Express with Advanced Services
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate