A last resort for corrupt datafiles with no backup: emergency mode, single user, then DBCC CHECKDB with repair_allow_data_loss. Back up the files first.
SQL SERVER – 2005 – Restore Database Using Corrupt Datafiles (.mdf and .ldf)
Can you restore database using corrupt datafiles when there is no full backup and both .mdf and .ldf are damaged? My honest answer and the one thing to try.
Rolling Back a Cumulative Update Safely
Rolling Back a Cumulative Update needs backups, setup evidence, a tested uninstall path, and special care for databases changed after patching.
SQL SERVER – Mirrored Backup Introduction and Explanation
SQL Server 2005 Enterprise and Developer editions support mirrored backup: one BACKUP DATABASE command with MIRROR TO writes the same backup to two places.
SQL SERVER – Solution – Log File Very Large – Log Full
Is your log file too big, or is the log full? Fix it in three steps: back up the log file, truncate it, then shrink it. I link my two detailed posts too.
SQLite or SQL Server Express for a Small App
SQLite or SQL Server Express depends on write concurrency, deployment, backup, and the growth path your small application really needs.
SQL SERVER – Shrinking Truncate Log File – Log Full – Part 2
About a year ago, I wrote SQL SERVER – Shrinking Truncate Log File – Log Full. I was just going through some of the earlier posts and comments.