Page 142 - DCAP508_DATABASE_ADMINISTRATION

Database Administration

Notes 10.2 Complete Database Backup

A complete database backup creates a stand-alone image of the entire database. A complete
database backup is self-dependent and may be restored to either the same or a new database on
the same or a different server. This provides plenty of flexibility at the time when this backup
has to be restored.
A complete backup may be restored without the need for any other kind of backup. It may also
be performed for databases in any recovery model. Restoring a complete database backup
typically would be considered a starting point for a disaster recovery situation where the entire
database is lost or damaged.
It is recommended that a complete database backup be performed at regular intervals for all
production databases. It is also recommended that a complete backup should be performed for
system databases (including master and MSDB) if there are any changes performed to the SQL
Server operating environment such as creating or removing databases, configuring security,
creating and modifying DTS packages or scheduled jobs, adding and removing linked servers,
etc.

10.2.1 Performing Complete Database Backups

A complete database backup may be performed either through SQL Server Enterprise Manager
or by using Transact-SQL commands. Complete backups may also be scheduled to be performed
at regular intervals. Scheduling may be done through either SQL Server Enterprise Manager or
using Transact-SQL commands.
To perform a complete database backup through SQL Server Enterprise Manager
1. Open Enterprise Manager and connect to the server.
2. Expand the Databases folder, then right-click the database that you want to back up.

Figure 10.1: Backup Database through Enterprise Manager

136 LOVELY PROFESSIONAL UNIVERSITY