Home

Backing up multiple databases

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



Another time saving feature in SQL Backup is the ability to back up multiple databases using a single command.  Using the standard T-SQL BACKUP syntax, you need to use multiple BACKUP commands to back up multiple databases e.g.

multidb_01

To perform the same backup using SQL Backup, you could issue the following single command:

multidb_02

Notice that we are using the <database> tag in order to dynamically specify the folder and file name, which is another SQL Backup feature.  In fact, if we wanted to back up all the databases on our SQL Server instance, we could do the following, again using just a single command:

multidb_03

Or we could do the inverse i.e. back up all but certain databases e.g.

multidb_04

There are also shortcuts to just back up all user databases, or all system databases.  To back up all user databases, use the BACKUP USER DATABASES command e.g.

retention05

To back up all system databases, use the BACKUP SYSTEM DATABASES command e.g.

retention04




Document history
5/8/2012    Added notes on USER and SYSTEM options.    
7/1/2010    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.