Transaction log backups on a schedule can miss a burst of activity that fills the disk. This post builds a procedure that reads the log written since the last backup and takes a log backup once it passes a limit you choose. It also explains why the old habit of shrinking the log after each backup does harm.
How to Shrink TempDB Without SQL Server Restart? – Interview Question of the Week #163
A client ran the shrink command again and again, but TempDB would not get any smaller. Here is how to Shrink TempDB without a SQL Server restart.
Restoring a Database That Has a Memory-Optimized Filegroup
The container behind a memory-optimized filegroup is a folder, and a restore must place it. Here is the error you get when you forget, and the fix.
Database File Size Shrinks by Itself? Check Auto Shrink
When a database file keeps getting smaller after you set its size, check Auto Shrink first. This post shows why a size you set later isn’t protected, then gives three checks: the database flag, jobs that shrink, and the default trace. It ends with the fix and the reason shrinking costs more than it saves.
SQL SERVER – FIX: The Log for Database Cannot be Shrunk Until All Secondaries Have Moved Past the Point Where the Log was Added
Shrinking a bloated AlwaysOn log gave me: the log cannot be shrunk until All Secondaries have moved past the point where the log was added. Here is the fix.
MSDB Growth From queue_messages: How to Clear the Queue
MSDB growth from the queue_messages tables means a Service Broker queue holds messages that nobody reads. This post builds a queue with unread messages in a test database, finds it with a size query, ends only its conversations with the CLEANUP option, and watches the space come back. It also says why you should never end every conversation in msdb.
Reverting a Failed Deployment With a Database Snapshot
A snapshot can undo a bad release in minutes. See what comes back, what is lost for good, and why your log backups need a fresh start.