17.06.2013 Views

Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 19: Playing Administrator<br />

And you’ll get a dialog box that lets you define pretty much all of the backup process as in Figure 19-15.<br />

Figure 19-15<br />

The first setting here is pretty self-explanatory — what database you want to back up. From there, however,<br />

things get a bit trickier.<br />

Getting into the items that may not yet make sense, first up is the recovery model. The Recovery Model<br />

field here is just notifying you what the database you’ve selected for backup is set to; it is actually a<br />

database-level setting. We’re going to defer discussion of what this is for a bit; we’ll get to it in the next<br />

section when we talk about backing up transaction logs.<br />

Now, those are the simple parts, but let’s break down some of the rest of the options that are available.<br />

Backup Type<br />

576<br />

First of the choices to be made is the backup type. Depending on the recovery model for your database<br />

(again, be patient with me, we’ll get there on what this is), you’ll have either two or three types of backups<br />

available:<br />

❑ Full: This is just what it sounds like: a full backup of your actual database file as it is as of the<br />

last transaction that was committed prior to you issuing the Backup command.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!