BUG: LOAD HEADERONLY Does Not Report the Correct Size of Dumps

• Microsoft SQL Server, version 6.5 Service Pack 2

SYMPTOMS

The LOAD HEADERONLY command does not report the correct size of a dump on the correct row of the query's results.

WORKAROUND

If you have more than one dump on the backup device, look at the next older dump's reported dump size for the size of the current dump. For the size of the last file on the device, look in the SQL Server errorlog, which will contain error 4035, or look at the client for error 4035, which does contain the correct dump size.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5 Service Pack 2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

For example, suppose you dump pubs and it reports 200 pages dumped, and then you dump master to the same device and it reports 6000 pages dumped. If you then dump pubs to the same device again, the LOAD HEADERONLY output would look similar to the following:

File Database Dumpsize ---- -------- --------

1     pubs      (null)
2     master    200
3     pubs      6000