BUG: Dump DB with INIT/UNLOAD May Fail to Execute in a Batch

  - Microsoft SQL Server version 4.2

SYMPTOMS

If a dump database <database_name> to <tapedevice> is made with INIT and/or UNLOAD in a single batch that contains multiple dump commands and the command to INIT and/or UNLOAD is not a part of the last dump command, the INIT and/or UNLOAD may not be performed. The INIT and/or UNLOAD in the last DUMP DATABASE statement will control how the previous dumps will be performed.

For example:

   use master
   go
   dump database master to tapedump with init,nounload
   dump database pubs to tapedump with noinit,unload
   go

The following batch script will not INIT the tape and will not unload as well:

NOTE: Both dumps will be appended to the current tape.

   use master
   go
   dump database master to tapedump with init,unload
   dump database pubs to tapedump with noinit,nounload
   go

   use master
   go
   dump database master to tapedump with noinit,nounload
   dump database pubs to tapedump with init,unload
   go

WORKAROUND

Separate each dump database to tape instruction with a delimiter. For ISQL.EXE, the appropriate delimiter is a 'go'.

STATUS

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