Adding a New Transaction Log File when the Existing Log is Full
SQL Server Transaction Log files store details about every change made to a SQL Server Data File. This includes when you need to add a 2nd log file. The act of adding a 2nd log…
Piecemeal Restore: Backup Set Holds a Backup of a Database Other than the Existing Database (Error)
When attempting to do a piecemeal restore of a database, using the ‘REPLACE’ option to replace the existing database, you may see the following error message: Msg 3154, Level 16, State 4, Line 63 The…
Full Recovery without Log Backups? Get Notified!
Why you need log backups in Full Recovery Model Databases in the Full Recovery Model1 log every transaction into the transaction log file. This enables point-in-time recovery2, which can be critical for meeting recovery-point objectives….
Optimal Log File Growth and Virtual Log Files
Intro The SQL Server Transaction Log is a critical component of each database, and should be managed pro-actively. Optimal log file growth is simple to setup, but knowing the right numbers to use for initial…
Storing Backups Locally? You have no Backups!
Me, being nice! You’ve got business critical data stored in your SQL Server, don’t you? And you’re taking backups of those databases, right? But where are you storing those backups? If you’re storing backups locally,…
Log Backup Failures - Danger, Will Robinson!
For databases in Full Recovery Model, log backups should be taken at a frequency that ensures your recovery point objective can be met. So you schedule log backups to occur, setup email notifications so you…