Home

Integrated database verification

Prev Page Next Page
Introduction
Recovery models
Main backup types
Backing up the database files by copying
The transaction log
Transaction log restore sequence
Log sequence numbers
Truncating and shrinking the transaction log
Backing up the tail
Inside the transaction log
So, what's in a backup file?
Test: A full backup does not contain deleted data
Verifying backup files
Verifying backup files on a budget
Cumulative backups
Recovering individual tables
Backup and restore history details
Backup reads and writes
Speeding up backups
Backup speed details
Speeding up restores
Restore state affects speed too
Backup and restore rights
Log shipping
Log shipping in SQL Server 2000
Setting up log shipping using Enterprise Manager
Checking the set up
Failover
Log shipping in SQL Server 2005
Setting up log shipping using Management Studio
Checking the set up
Log shipping status report
Failover
Log shipping in SQL Backup
Using the CopyTool utility
Failover
3rd party backup applications
VDI
VDI versions
VDI errors
SQL Backup - beyond compression
Restoring a chain of transaction log backups
Restoring to the latest possible state
Backing up multiple databases
Backup retention
Making a copy of the backup file
Backup file naming conventions
Restoring the latest backup set
Network resilience
Encryption
Integrated database verification
Database file relocation
Improved backup retention
RESTORE HELP
High-availability group support
Common SQL Backup issues
Installation checklist
Setting up rights
Configuring service rights
Backup data
Hanging issues
Common backup and restore errors
Error 3201 - when performing a backup to a network share
Full database backup file is larger than database size
Error 3205 - Too many backup devices specified for backup or restore
Error 4305 - an earlier transaction log backup is required
Bringing a database that is in recovery or read-only mode online
Using bulk-logged recovery model but transaction log backup is still large
Error 14274 - unable to delete SQL Server Agent job
Error messages when restoring from different versions of SQL Server.
Pending
vdi error codes
Restore speed details
Help, my transaction log file is huge!
Mirror or log ship



# available only in SQL Backup 7.0 and newer

To ensure that a backup file is valid, you would need to restore it. To ensure that the restored database is structurally valid, you would run the DBCC CHECKDB command.  SQL Backup allows you to perform the above 2 verification steps in a single RESTORE command.

To run a DBCC CHECKDB on the restored database, simply use the CHECKDB option e.g.

checkdb01

 

SQL Backup then runs the DBCC CHECKDB command on the restored database once the restore has completed, and reports the results.  In the case of a successful check, something like this is displayed:

checkdb02

 

If there were errors, SQL Backup reports the errors e.g.

checkdb03

By default, SQL Backup uses the NO_INFOMSGS option for the DBCC CHECKDB command.  You can use the usual DBCC CHECKDB options in your RESTORE command e.g.

checkdb04

 

 

To extend the usefulness of this feature further, you have the option of dropping the database after the consistency checks have completed, by using the DROPDB option e.g.

checkdb05

Or if you want to drop the database only if the consistency checks completed successfully, you can also do so using the DROPDBIFSUCCESSFUL option e.g.

checkdb06




Document history
5/7/2012    Initial release.    
 
Copyright 2008 - 2017 Yohz Ventures Sdn Bhd. All rights reserved.
All product and company names are trademarks or registered trademarks of their respective owners.