BUG: SQL Admin Unable to Load Tape Dump with Different Names

Last reviewed: April 29, 1997
Article ID: Q113066

The information in this article applies to:

  - Microsoft SQL Server Programmer's Toolkit, version 4.2
BUG# 9876 (4.2)

SYMPTOMS

Using the SQL Administrator for Windows to load a dump from tape requires that the user read the tape to scan for dump files on that tape. The pick box will only list dumps that have the same or similar names to the database being loaded.

For instance, if you are trying to load a dump into PUBS, the list will include dumps from databases named PUBS or PUBS2, but not list dumps from databases name TEST. There is no way to manually insert a dump file number so you can not load using the pull down menus.

WORKAROUND

You can use a query window or ISQL to explicitly LOAD the correct dump file, then use the CONSOLE program to manage interaction with the tape unit. For instance, if you have a dump of database TEST that you want to load into database PUBS, and the dump is the second file on the tape, you would issue the command:

   LOAD DATABASE pubs FROM tape0 WITH FILE=2

STATUS

Microsoft has confirmed this to be a problem in SQL Administrator version 4.2 for Windows NT and SQL Administrator for Windows. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words:
Keywords : kbbug4.20 kbtool SSrvSQL_Admin
Version : 4.2
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 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.