FIX: Database Dumps May Be Overwritable Despite Options

• Microsoft SQL Server version 6.5
• Microsoft SQL Server, Enterprise Edition, version 6.5

SYMPTOMS

The DUMP statement has two options, EXPIREDATE and RETAINDAYS, that are intended to prevent database or transaction log dumps from being overwritten when a DUMP statement with the INIT option is subsequently used. However, these options do not work properly when the date specified is after December 31, 1999.

WORKAROUND

To work around this problem, after dumping your database or transaction log, copy the dump file to another location.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 5a for Microsoft SQL Server version 6.5. For information about downloading and installing the latest SQL Server Service Pack, see http://support.microsoft.com/support/sql/.

For more information, contact your primary support provider.

MORE INFORMATION

The symptoms described in this article can affect either tape or disk dumps.

The dump header information (either tape or disk) has a field reserved for ExpireDate. This date is set by using either the EXPIREDATE or RETAINDAYS dump options. When the date is later than December 31, 1999, the ExpireDate field is set to NULL, thus permitting subsequent DUMP statements (with INIT) to be allowed.

The ExpireDate field can be examined on any dump file with the LOAD HEADERONLY command.

For the syntax and further explanation of the DUMP statement and the EXPIREDATE and RETAINDAYS options, please see the SQL Server Books Online.

Additional query words: prodsqlsp sp5Year 2000 y2k 2k

Keywords          : SSrvAdmin kbbug6.50 kbfix6.50.SP5 
Version           : winnt:6.5
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: April 4, 1999