Build a backup strategy and restore plan from scratch
If you have a SQL Server you must have a backup and restore plan. If you don’t you’re in for a rude awakening for sure.… Read More »Build a backup strategy and restore plan from scratch
If you have a SQL Server you must have a backup and restore plan. If you don’t you’re in for a rude awakening for sure.… Read More »Build a backup strategy and restore plan from scratch
Steve Stedman 0:15 So Derrick, one of the things we run into is customers who are a little bit resistant to running CheckDB as frequently… Read More »CheckDB Chat with Steve and Derrick
As a DBA you regularly schedule backups you might have regular full backups, incremental backups and hopefully regular backups. Over time you might realize that your error log is not longer filled with errors, but instead a majority of your error log is filled with backup messages. “Backup Database successfully … “, “Database backed up…”, “Log was backed up”. This makes it a bit difficult to find the actual errors in this flood of backup messages. Your error log is no longer an error log, but it looks more like a backup log.
Trace flags in SQL Server are switches or parameters that can be used to turn on or off different features. If you use trace flag 3226 this will turn off all successful backup messages being written to the error log. There are a couple of ways to use trace flag 3226, one is to use DBCC TRACEON to turn on trace flag 3226 for the currently running instance. Using this option will turn it on until the next time the database instance is restarted.
Read More »Silencing Backup Messages with Trace Flag 3226