Hot SQL Server backup concerns

Hot SQL Server backup concerns

What happens when users are working during a SQL Server 2000 backup?

    Requires Free Membership to View

    When you register for SearchDataBackup.com, you’ll also receive targeted emails from my team of award-winning editorial writers. Because your job never seems to get any easier, it’s our goal to keep you up-to-date on the latest backup tips, trends and technologies that will help you get the job done.

    Rich Castagna, Editorial Director

    By submitting your registration information to SearchDataBackup.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchDataBackup.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

When SQL Server does an online hot backup, users can continue normal transaction activity. During the backup operation, updates are logged within SQL Server's transaction log. Reduced database performance is the most likely issue when backing up SQL Server while the database is online and being used actively.

The degree of impact will depend on the power of your server hardware (CPU, memory, etc), speed of your backup infrastructure and the volume of transactions hitting the database. If you have a very busy SQL Server, you will have to ensure that your infrastructure is tailored to handle the high volume of transactions while it is also being backed up in order to provide response times that are up to your users' expectations.

Do you know…

How to plan a records retention program?

This was first published in June 2006