Home > Articles > Data > SQL Server

Backing Up and Restoring in SQL Server

Have you ever been confused about which backup goes with which recovery model? In this excerpt from his book, Essential SQL Server 2000: An Administration Handbook, Buck Woody explains the concepts of backing up databases, and the models used for each type of backup.

This article is excerpted from Essential SQL Server 2000: An Administration Handbook (Addison Wesley, 2001, ISBN: 0201742039).

This chapter is from the book

In its simplest form, the database backup and restore procedure for SQL Server 2000 is incredibly easy. One command or just a few clicks in Enterprise Manager performs a backup or restores one. You can make these backups to disk, network shares, or tape.

If you need a test database to play with, you can easily get one by backing up the current database and restoring it with another name. You don't have to create a set of special files first, or make any other changes to your database server to do this. As a matter of fact, the users don't even have to be out of the database while you're backing it up, although that's usually a good idea anyway. Both the backup and the user activity will be slightly slower during backup.

Once the database is backed up, it's an equally simple matter to restore it, even to another server. Of course, during a restore, the users cannot access the database.

Backups can be taken graphically or with the command line tools, and they can also be scheduled.

The backup and restore process really isn't that difficult, and they are usually quite fast. Even so, large databases, in the multi-gigabyte range, can take more than a few hours to complete. You might wonder what data is stored in the backup file if the backup starts at midnight but it doesn't complete the backup until one in the morning, and people are still entering data in the database. The answer is the last piece of data that makes it into the database at one in the morning.

Backing Up Databases

Even though backing up a simple database is easy, rarely are things in their simplest form.

One of the primary variables that will affect your backup is the size of the database. Obviously, a bigger database means a longer, larger backup. If a database is quite large, it may not fit on a single tape or one drive location. This lengthier backup may also take more time than available to complete the backup.

To deal with these issues, SQL Server 2000 provides the ability to stripe backups across multiple tapes or disk devices, so that several devices can be combined to deal with the size and time factors.

You can also structure your backups so that only the changes since the last backup are included, which helps you deal with the size and time elements.

Recovery Models

The next factor that will affect your backups is the recovery model.

In most cases, when data is written to a SQL Server 2000, it is written not to the database, but to a separate file called the log.

This log file contains all the individual data transactions, and a logging process writes those changes to the database. The committed data items are then marked to indicate they made it into the database, a process called a checkpoint. The recovery model determines what happens next.

If the database has been set to the Simple recovery model, the marked data is erased from the log file after the change is written successfully to the database. In that way, the log shrinks and expands automatically, if the database option auto shrink is on.

If the Bulk-Logged model is selected for the database, then changes are not erased after they make it to the database until you back up the database or log. Certain bulk-load operations are not completely logged, so all data may not make it to the log backups. Recovery can as recent as the last log backup.

If the Full model is selected for the database, then the changes are not erased after they make it to the database, and are only erased when you back up the database or log.

In this model, all operations are logged, so all data makes it to the log backups. This slows the process of bulk-logged operations, but is safer. Recovery can as recent as the last log backup or to a specific point in time.

Full Backups

As an example, imagine a database set to the Simple recovery model. You perform a full backup at midnight when no one is using the database, and people start to enter data again at 7:00 in the morning.

At 11:01, your server catches on fire, and after it is replaced, the backup you restore brings you to a current state as of midnight the night before.

Log Backups

Next, imagine the database is set to use the Full recovery model. You make that same midnight backup, and then every two hours, starting at 7:00, you make a separate backup of the log.

A fire breaks out again at exactly 11:01. This time, however, you restore that midnight backup, making you current as of midnight.

Next you apply the 7:00, 9:00, and then the 11:00 log backups in that order.

You've now lost only one minute's work.

Large Backups

The recovery model not only affects what level of recovery you can achieve, but also the time it takes to create your backup.

With the database set to Simple recovery, you must perform a full backup of the database with exceptions, which may take a while if the database is huge, in the multi-gigabyte range.

With the database set to the Full or Bulk-Logged model, you would perform that lengthy full backup only periodically, and you perform periodic log backups that take very little time because they contain only the changes.

To restore the database to a good state, you would restore the full backup and then each log backup in order, starting from the earliest log backup.

The other side of that coin is that it takes a bit longer to restore under the latter model because you have to do all the log restores in order.

Differential Backups

I mentioned an exception earlier. The exception involves something called a differential backup. This is sort of like an extended log backup (except in the Simple model), in that it backs up just the changes, but it's all the changes since the last full backup. This type of backup can be used with any of the recovery models.

Let's return to the combustible server example to illustrate. In the Simple recovery model, you back up the database at midnight, as before. This time, however, you take a differential backup at 10:00, intending to do so every four hours thereafter.

The server is again well engulfed in flames by 11:01, but this time, you are safe as of 10:00. What you have to do at this point is to restore the full backup of midnight and then the differential one from 10:00.

In the Full and Bulk-Logged models, assuming a large database, the strategy is that a full backup is taken on the weekend, which gets all data.

Logs are backed up every two hours as usual, but because the database is so large, you would have to apply the full restore, and then far too many log backups to be comfortable.

The answer to this dilemma is to perform a differential backup each night, which gets all the changes since the last full backup. You now don't need the log backups between the time you took the full and differential backups, since the differential backup is a kind of combined log backup. This strategy allows you to restore the full backup, the differential backup, and then only the log backups since the differential backup. The restore time in this model takes a lot less time. The tradeoff here is that the differential backups can become quite large.

Backup Locations

Assuming that you've installed the required tape hardware and drivers on your NT or Windows 2000 system, you can send your backups there.

The first tape drive is referred to as \\.\TAPE0, replacing the 0 with the next number (1,2,3, etc.) for the other tape drives you have on your system. The tape drives must be physically located on the server to do this, so you can't use remote tape drives with SQL Server 2000's native backup commands.

SQL Server 2000 backups can exist on the same tape as a Windows NT backup made with the NTBACKUP command, but you'll want to put the SQL backup on first, and set the backup switch that doesn't rewind the tape. Personally, I don't use this feature; always feeling a bit insecure about how much room will be left on the tape for either backup.

The other option is to send the backup directly to disk, specifying the path and filename directly. Your NT backup program can back up these files since they aren't in use. In this model you'll want to carefully monitor your drive space, and a good compression utility can bring the size of the .BAK file to less than 25 percent of its original size.

Backup Devices

Not only can you send the backup file directly to tape or hard drive paths, but you can also specify a friendlier name by creating a logical device.

Recovery Process

You can recover a database using Enterprise Manager or Query Analyzer. The types of commands involve the recovery model of the database.

If the recovery is set to the Simple model, the recover process involves restoring the last full backup, leaving the database in a usable mode. This effectively closes the database and allows connections from users.

If the recovery model is set to Full or Bulk-Logged, the recovery involves restoring the last full backup, and leaving the database non-operational but able to restore log backups. To complete the backup, you restore the logs, in order, from earliest to last. At the last log restore, you leave the database operational.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020