Prev Page Next Page
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
Log shipping in SQL Server 2005
Setting up log shipping using Management Studio
Checking the set up
Log shipping status report
Log shipping in SQL Backup
Using the CopyTool utility
3rd party backup applications
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
Integrated database verification
Database file relocation
Improved backup retention
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.
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

The following is not a supported feature in SQL Backup, but it's there.

You want to restore a full database backup, but want to move the data and log files to different locations from the original.  Your database contains multiple data files, and you need to move them one by one e.g.



That's a lot of typing, more so if your database contains an even larger number of files.  The usual practice is to run the RESTORE FILELISTONLY command to get a list of the database files, and copy/paste the file names into your restore command.  If you just wanted to move all the data files to one directory, you could use SQL Backup's MOVE DATAFILES option.  However, you cannot use that option if you want to move the data files to various different directories.

What if you could do this instead:



and get the following output:



Then all you have to do is to make your changes, edit the restore template so that it can be ran as a SQL Backup command (remove the commented lines and replace the single quotes with 2 single quotes), and you're done.  Note that the template also tells you how much space each file requires, so you can organize your files better.

Finally, RESTORE HELP works for native backup files too, even those containing multiple backup sets.  E.g.





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