FIX: Temporary Dump Devices May Be Created with the Wrong Name

Last reviewed: June 27, 1997
Article ID: Q161599
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5
BUG #: 15681 (6.0)
       16411 (6.5)

SYMPTOMS

If temporary disk dump devices are used that contain spaces in the path or file name, the dump file may be created in the incorrect directory, or may be created with the incorrect name. However, the dump is valid to load if the file is specified correctly.

WORKAROUND

To work around this problem, do either of the following:

  • Create disk dump devices with the stored procedure sp_addumpdevice or SQL Enterprise Manager, and then dump and load with the device name rather than using the temporary dump device syntax.

    -or-

  • Do not use spaces in the path or file name for temporary disk dump devices.

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 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

MORE INFORMATION

Temporary disk dump devices are created by using the DISK="<filename>" for the dump device.

The following example illustrates the problem:

   DUMP DATABASE pubs TO DISK='c:\mssql\backup\disk test.dat'

Instead of creating a dump file named "disk test.dat," a file called "disk." is created.


Additional query words: headeronly
Keywords : kbbug6.00 kbusage SSrvAdmin SSrvEntMan SSrvGen SSrvStProc
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: June 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.