INF: Correction for Microsoft SQL Server 2000 Resource Kit (311115)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q311115

SUMMARY

This article contains a correction and information about an error message that relates to the Microsoft Press book "Microsoft SQL Server 2000 Resource Kit"; ISBN 0-7356-1266-8.

MORE INFORMATION

In the "Microsoft SQL Server 2000 Resource Kit", page 385, in the "Generating Database Backups from the Secondary" topic, the first sentence of the topic states:

Since the log shipped database is only a small increment of time out of sync with the primary database, it is a good idea to use it to generate the full database backups.

The preceding statement implies that you can back up the log shipped database on the secondary server, which is incorrect. The log shipped database on the secondary server is in a read-only state and you cannot use that database to generate any type of SQL Server backup.

The Log Shipping process leaves the database on the secondary server in either a STANDBY or a LOADING status depending upon which option you select when you configure Log Shipping. Both STANDBY and LOADING are read-only states, which prevents any writes to the transaction log. Because the backup process needs to log its operations (backup history), and changes to the transaction log are disallowed, SQL Server does not allow you to perform backups performed against a log shipping secondary database.

Modification Type:MinorLast Reviewed:9/14/2006
Keywords:kbinfo KB311115