Beware – REPAIR_ALLOW_DATA_LOSS Vs REPAIR_REBUILD
When you hear checkdb repair_allow_data_loss it can sound like a good thing, but please read on, that is not at all true. So, you have… Read More »Beware – REPAIR_ALLOW_DATA_LOSS Vs REPAIR_REBUILD
Database Corruption Repair
Basics of Database Corruption Repair
Please join me on Saturday March 16 in Victoria BC Canada for my SQL Saturday presentation on the Basics of Database Corruption Repair. Here is… Read More »Basics of Database Corruption Repair
Silencing Backup Messages with Trace Flag 3226
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 Flag 3226
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