Article ID: 161599
Article Last Modified on 10/16/2003
APPLIES TO
- Microsoft SQL Server 6.0 Standard Edition
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q161599
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: kbfix kbusage KB161599
