The database is technically online but inaccessible to users. You will see it in SSMS Object Explorer with a yellow warning icon and (Recovery Pending) next to its name.
-- 1. Take database offline (force close any lingering handles) ALTER DATABASE YourDatabaseName SET OFFLINE;
-- Shrink log if possible (after freeing disk space) DBCC SHRINKFILE (YourDatabaseName_log, 1024); -- Target 1 GB
| Practice | Implementation | |----------|----------------| | | Run every 15–30 minutes for full recovery model | | Monitor disk space | Alert when log drive <10% free | | Do not manually delete .ldf files | Ever. Use ALTER DATABASE ... MODIFY FILE to relocate | | Test restores | Monthly restore drills validate backup integrity | | Set database to SIMPLE recovery if point-in-time recovery not required | Reduces log management complexity | | Use DBCC CHECKDB weekly | Catches corruption early |
Contact Microsoft CSS if:
If the drive housing your data or log files is full, SQL Server cannot initialize the recovery process.
The database is technically online but inaccessible to users. You will see it in SSMS Object Explorer with a yellow warning icon and (Recovery Pending) next to its name.
-- 1. Take database offline (force close any lingering handles) ALTER DATABASE YourDatabaseName SET OFFLINE;
-- Shrink log if possible (after freeing disk space) DBCC SHRINKFILE (YourDatabaseName_log, 1024); -- Target 1 GB
| Practice | Implementation | |----------|----------------| | | Run every 15–30 minutes for full recovery model | | Monitor disk space | Alert when log drive <10% free | | Do not manually delete .ldf files | Ever. Use ALTER DATABASE ... MODIFY FILE to relocate | | Test restores | Monthly restore drills validate backup integrity | | Set database to SIMPLE recovery if point-in-time recovery not required | Reduces log management complexity | | Use DBCC CHECKDB weekly | Catches corruption early |
Contact Microsoft CSS if:
If the drive housing your data or log files is full, SQL Server cannot initialize the recovery process.