SQL CMD

Connection Problems

Clearing the transaction log

Rebuild SQL Server Master Databases in Less than 5 Minutes

How to rebuild your master database quickly and safely.

(new) Kill ALL Connections To a SQL Database

Ever puzzled by the database "Currently in Use" error even though you thought all connections had been Killed? That’s because the wrong table SysProcesses was used.

sys.objects

Corruption Detection

Transaction Log Files

Tempdb

Making a more reliable and flexible sp_MSforeachdb

While the system procedure sp_MSforeachdb is neither documented nor officially supported, most SQL Server professionals have used it at one time or another. This is typically for ad hoc maintenance tasks, but many people (myself included) have used this type of looping activity in permanent routines. Sadly, I have discovered instances where, under heavy load and/or with a large number of databases, the procedure can actually skip multiple catalogs with no error or warning message. Since this situation is not easily reproducible, and since Microsoft typically has no interest in fixing unsupported objects, this may be happening in your environment right now