PRB: RESTORE WITH STANDBY Does Not Catch Invalid or ReadOnly File Name Until After the Load (264593)


The information in this article applies to:

  • Microsoft SQL Server 7.0
  • Microsoft SQL Server 2000 (all editions)
This article was previously published under Q264593

SYMPTOMS

When you perform a RESTORE WITH STANDBY = <undofilename> and the file name is either invalid or has permissions problems, error messages similar to the following example (from an attempt to restore the Northwind database by using a standby file set to ReadOnly) occur:
Processed 6368 pages for database 'northwind', file 'Northwind' on file 1.
Processed 1 pages for database 'northwind', file 'Northwind_log' on file 1.
Server: Msg 3441, Level 17, State 1, Line 1
Database 'Northwind' (database ID 6). The RESTORE statement could not access file 'c:\standby1.undo'. Error was '5(Access is denied.)'. Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE terminating abnormally.

MORE INFORMATION

Please note that although this error is not caught until after all the data pages have loaded, the operation can be completed without reloading any of the data pages so that you do not waste any time. The database is left in a loading state. To complete the RESTORE WITH STANDBY, re-run the RESTORE command, as follows, after either correcting the file name or the permissions: 
RESTORE DATABASE <datasebasename>
WITH STANDBY='<filename>'
Modification Type:MajorLast Reviewed:10/17/2003
Keywords:kbprb KB264593
©2003 Microsoft Corporation. All rights reserved.