Blocking in SQL Server is normal behavior, but excessive blocking can lead to many complaints and is a symptom of poor performance. SQL Server contains a vast amount of information that can help when troubleshooting performance issues like blocking, but understanding and gathering that information when you need it is a lot of work. Darko Martinovic explains his solution for a custom blocking report.
Every DBA squirrels away favourite queries for monitoring SQL Server. Nowadays many of these are too complex to keep in your head. Dennes describes how he uses T-SQL queries for solving problems, whether it involves fixing the problems of missing indexes, preventing unrestrained autogrowth, avoiding index fragmentation, checking whether jobs have failed or avoiding memory stress conditions.
This free guide includes worked examples, practical advice, and covers the hows and why of SQL Server monitoring. Download the guide and get a 26 monitoring tips as well.
If looking after the health of SQL Server is part of your responsibility, Redgate would love to hear your views on monitoring server health through this 10 minute survey. Complete the survey by May 15th to be in with the chance to win one of three $50 Amazon vouchers.
SQL Server Data Collector, together with Management Data Warehouse, is a fine and useful component for gathering information centrally about how SQL Server instances are being used, and thereby keeping an eye out for problems. It comes into its own when you have figured out how to configure it to run on maybe hundreds of instances using Central Management Server. Dennes describes how to tame the system so that it scales.