It’s crucial for database administrators to recognize signs of pending doom. Make sure you’re able to quickly spot problems in SQL Server Management Studio by studying these screenshots.
What’s that? You can’t see the differences in the screenshots? That’s because SQL Server Management Studio doesn’t show you serious problems.
The more I learn about SQL Server and the more customer servers I examine, the more frustrated I get with SQL Server Management Studio. It’s the year 2012, and the product’s been out for well over a decade – yet dangerous settings like Priority Boost and Lightweight Pooling don’t even have warnings in the GUI. Just enable ‘em, click OK, and your server’s performance and reliability can go right down the toilet without so much as a warning icon in SSMS.
When you’re facing performance or reliability problems, your first step should be to run our free sp_Blitz stored proc to show you this stuff. It just breaks my heart when we do our SQL Server health checks, find these problems within the first few minutes, and everyone’s surprised that someone enabled these obscure options long ago without telling anyone.
sp_Blitz: because no one likes zombie cockroaches in the database server.