Happy holidays! Santa SQL comes bringing tidings of cheer with a new sp_Blitz® – but also doom and gloom about configuration problems in your servers. Here’s some of the recent contributions from readers:
- John Miner suggested tweaking checkid 48 and 56, the untrusted constraints and keys, to look for is_not_for_replication = 0 too. This filters out constraints/keys that are only used for replication and don’t need to be trusted.
- Ned Otter caught a bug in the URL for check 7, startup stored procs.
- Scott (Anon) recommended using SUSER_SNAME(0x01) instead of ‘sa’ when checking for job ownership, database ownership, etc.
- Martin Schmidt caught a bug in checkid 1 and contributed code to catch databases that had never been backed up.
- Added parameter for @CheckProcedureCache. When set to 0, we skip the checks that are typically the slowest on servers with lots of memory. I’m defaulting this to 0 so more users can get results back faster.
- Andreas Schubert caught a typo in the explanations for checks 15-17.
- K. Brian Kelley added checkid 57 for SQL Agent jobs set to start automatically on startup.
- Added parameter for @CheckUserDatabaseObjects. When set to 0, we skip the checks that are typically the slowest on large servers, the user database schema checks for things like triggers, hypothetical indexes, untrusted constraints, etc.
- David Tolbert caught a bug in checkid 2. If some backups had failed or been aborted, we raised a false alarm about no transaction log backups.
- Fixed more bugs in checking for SQL Server 2005. (I need more 2005 VMs!)
- Ali Razeghi added checkid 55 looking for databases owned by <> SA.
- Fixed bugs in checking for SQL Server 2005 (leading % signs)
Whew! And there’s more to come – I’ve got another half-dozen improvements queued up that also require new web pages, so those will take a little while longer.
If you’ve already downloaded sp_Blitz®, you can run master.dbo.sp_BlitzUpdate to fetch the latest version from The Clouds. Enjoy!