FIX: LOAD HEADERONLY Doesn't Report Files Cont on Another Tape

 Last reviewed: April 8, 1997
Article ID: Q150891

The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 & 6.5
BUG#: 15076 (6.00)

SYMPTOMS

The Dump Database command can continue or span a dump across multiple tapes. If the Load Headeronly command is used to verify the dump, it will not report files that span tapes.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.0 and 6.5. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

MORE INFORMATION

Consider the following scenario. The master, pubs, and a user database are dumped to a tape with a capacity of 1 GB and the user database has 1.5 GB space used. In this situation, the dump of the user database can not complete on the first tape but will complete if a second tape is mounted. If Load Headeronly is run on the first tape, it will report that 2 files exist on the tape containing dumps of the master and pubs databases. If Load Headeronly is run on the second tape, it will report that 0 files exist on the tape.

Additional query words: span
Keywords : kbbug6.00 kbbug6.50 kbfix6.50.sp2 kbusage SSrvAdmin
Version : 6.0 6.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.