My new sp_Blitz® stored procedure helps you take over SQL Servers, identify risks, and build an inventory of what needs to be fixed. Here’s the video from our Tech Tuesday Triage webcast series this week when I explained how to use it:
In the sp_Blitz® output, I include a link to learn more about each problem on your server. Thanks to the magic of web site analytics, I can see the most popular issues.
- Slow Storage Reads or Writes – so often, our biggest bottleneck is storage.
- Untrusted Foreign Keys or Check Constraints – I just recently started checking for this problem myself, and it’s popping up everywhere.
- Single-Use Plans in the Procedure Cache – just one isn’t a problem, of course, and the severity of the problem is based on the number you have and the size of memory they take up. Those numbers are listed in the sp_Blitz® output.
- Databases Owned by Users <> SA – and I love that this one hit the top 5 because it was our first user-contributed query in sp_Blitz®, sent in by Ali Razeghi.
- Triggers Found on Tables – no surprise there because this was one of the reasons I first started writing my Blitz scripts. My developers were troubleshooting problems with insert/update statements and had no idea someone else had written a trigger to modify their data.
Those are just five of the checks – and there’s already over fifty. If you’d like to add a check, email me with your script and the permission to use it, and I’ll add it into sp_Blitz® too.