sp_blitz

New Updates for sp_Blitz®, sp_BlitzCache™

SQL Server
24 Comments
We’ve just updated our First Responder Kit to include new versions of these tools: sp_Blitz® v41 – June 18, 2015: Added check 162 for CMEMTHREAD waits on servers with >= 8 logical processors per NUMA node. Added check 159 for NUMA nodes reporting dangerously low memory in sys.dm_os_nodes. Added check 161 for a high number of cached…
Read More

New sp_Blitz® and sp_BlitzCache® Updates

SQL Server
16 Comments
Ah, spring, when a young man’s fancy lightly turns to thoughts of updating his DMV queries. sp_Blitz®, our free health check stored procedure, brings several new checks and a whole crop of fixes and improvements. I’d like to call your attention to one in particular. Julie Citro fixed check 1, THE VERY FIRST CHECK IN THE…
Read More

sp_Blitz® v22: Output Results to a Table, Better Comments, and an App

SQL Server
40 Comments
Our free server troubleshooting tool, sp_Blitz®, just learned some new tricks. If you call it like this: EXEC dbo.sp_Blitz @OutputDatabaseName = ‘DBAtools’, @OutputSchemaName = ‘dbo’, @OutputTableName = ‘BlitzResults’ It will create the table DBAtools.dbo.BlitzResults (if it doesn’t already exist) and insert the results. The table includes columns for the server name and the check date,…
Read More

sp_Blitz® Version 18 Out: Lots of Bug Fixes

SQL Server
14 Comments
There’s a new version in town.  v18 adds new checks looking for: Backups stored on the same drive letters as user databases (Thanks @AlinSelicean!) Agent jobs that don’t have failure notifications set up (Thanks @Thirster42!) Shows free drive space per drive letter if you pass @CheckServerInfo = 1 in. We don’t consider this a problem…
Read More

Recognizing SQL Server’s Warning Signs

SQL Server
15 Comments
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. Databases that haven’t been backed up in 24 hours Databases with old compatibility levels Databases running out of space on the C drive SQL Server with Priority…
Read More

How to BACKUP LOG WITH TRUNCATE_ONLY in SQL Server 2008, R2, 2012, 2014, 2016, 2017, 2019

BACKUP LOG WITH TRUNCATE_ONLY is a dangerous command: it empties out the contents of your SQL Server’s transaction log without really backing it up.  Database administrators sometimes run this command right before shrinking their log file with a DBCC SHRINKFILE command, thereby freeing up drive space. Why ‘truncate_only’ is not a recognized backup option. When…
Read More