You are currently offline, waiting for your internet to reconnect

FIX: SQL Server Does Not Run RESTOREVERIFYONLY When Scheduling a Back Up in SQL Enterprise Manager

This article was previously published under Q279015
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 57268 (SQLBUG_70)
BUG #: 218599 (SHILOH_BUGS)
SYMPTOMS
If you back up a database with SQL Enterprise Manager (SEM) and you check Verify backup upon completion under the Option tab, SQL Server issues the following commands: BACKUP DATABASE and RESTORE VERIFYONLY. RESTORE VERIFYONLY checks whether the backup set is complete and whether all volumes are readable.

For example, if you back up the Pubs database to a backup device called Test, SQL server runs the following two SQL commands:
BACKUP DATABASE [pubs] TO [test] WITH  INIT ,  NOUNLOAD ,  NAME = N'pubs backup',  NOSKIP ,  STATS = 10,  NOFORMAT goRESTORE VERIFYONLY FROM [test] WITH  FILE = 1 ,  NOUNLOAD				
However, if you schedule a job through the SQL Enterprise Manager to do the same database back up, SQL Server only schedules BACKUP DATABASE without the RESTORE VERIFYONLY option.
RESOLUTION

SQL Server 2000

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

SQL Server 7.0

To resolve this problem, obtain the latest service pack for SQL Server 7.0. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301511 INF: How to Obtain the Latest SQL Server 7.0 Service Pack
WORKAROUND
Because the scheduled backup job does not do the verification, you can change the job step manually from
BACKUP DATABASE [pubs] TO [test] WITH  INIT ,  NOUNLOAD ,  NAME = N'pubs backup',  NOSKIP ,  STATS = 10,  NOFORMAT				
to:
BACKUP DATABASE [pubs] TO [test] WITH  INIT ,  NOUNLOAD ,  NAME = N'pubs backup',  NOSKIP ,  STATS = 10,  NOFORMATDECLARE @i INTselect @i = position from msdb..backupset where database_name='pubs'and type!='F' and backup_set_id=(select max(backup_set_id) from msdb..backupset where database_name='pubs')RESTORE VERIFYONLY FROM  [test]  WITH FILE = @i				
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

SQL Server 2000

This problem was first corrected in SQL Server 2000 Service Pack 1.

SQL Server 7.0

This problem was first corrected in SQL Server 7.0 Service Pack 3.
Properties

Article ID: 279015 - Last Review: 01/16/2015 21:01:59 - Revision: 3.2

Microsoft SQL Server 7.0 Standard Edition, Microsoft SQL Server 2000 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB279015
Feedback