You may receive an error message when you try to restore a SQL Server 7.0 database backup on an instance of SQL Server 2000

Article translations Article translations
Article ID: 837938 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

When you try to restore a Microsoft SQL Server 7.0 database backup on an instance of SQL Server 2000, the restoration operation may not be successful. You may receive an error message that is similar to the following:
Processed 160 pages for database 'Database name', file 'Database name' on file 1.
Processed 1 pages for database 'Database name', file 'Log file name' on file 1.
Server: Msg 3624, Level 20, State 1, Line 1

Converting database 'Database name' from version 515 to the current version 539.
Database 'Database name' running the upgrade step from version 515 to version 524.
Database 'Database name' running the upgrade step from version 524 to version 525.
Database 'Database name' running the upgrade step from version 525 to version 526.
Database 'Database name' running the upgrade step from version 526 to version 527.
Location: upgraddb.cpp:1430
Expression: PageId_FIRST_SYSOBJECTS_AFTER_527 == newPageId
SPID: 52
Process ID: 1548

Connection Broken
Note This problem occurs when trace flag 1118 is turned on for your instance of SQL Server 2000.

WORKAROUND

To work around this problem, turn off trace flag 1118, and then restore the SQL Server 7.0 database backup. After you successfully restore the SQL Server 7.0 database backup, you can turn on trace flag 1118. To do so, follow these steps:
  1. Start SQL Query Analyzer, and then connect to your instance of SQL Server 2000.
  2. Run the following Transact-SQL statement to turn off trace flag 1118 on your instance of SQL Server 2000:
    DBCC TRACEOFF (1118)
  3. Restore the SQL Server 7.0 database backup. For more information, visit the following Microsoft Web site:
    http://msdn2.microsoft.com/en-us/library/aa196683(SQL.80).aspx
  4. Run the following Transact-SQL statement to turn on trace flag 1118 on your instance of SQL Server 2000:
    DBCC TRACEON (1118)

MORE INFORMATION

Steps to reproduce the problem

  1. Start SQL Query Analyzer, and then connect to your instance of SQL Server 7.0.
  2. Take the backup of the Pubs database from your instance of SQL Server 7.0.
  3. Close SQL Query Analyzer.
  4. Start SQL Query Analyzer, and then connect to your instance of SQL Server 2000.
  5. Turn on trace flag 1118 for your instance of SQL Server 2000. To so do, run the following Transact-SQL statement:
    DBCC TRACEON (1118)
    GO
  6. Restore the SQL Server 7.0 database backup that is taken in step 2.

    You receive the error message that is mentioned in the "Symptoms" section of this article.

REFERENCES

For additional information about trace flag 1118, click the following article number to view the article in the Microsoft Knowledge Base:
328551 FIX: Concurrency enhancements for the tempdb database
For additional information about other problems that may occur when you restore a SQL Server 7.0 database backup, click the following article numbers to view the articles in the Microsoft Knowledge Base:
811478 FIX: Restoring a SQL Server 7.0 database backup in SQL Server 2000 Service Pack 2 (Ss) may cause an assertion error in the Xdes.cpp file
833547 FIX: Restoring a SQL Server 7.0 database backup in SQL Server 2000 Service Pack 3 (SP3) may cause an assertion error in the Xdes.cpp file
814579 PRB: You receive error message: "The log file for database 'Database Name' is full" while restoring a SQL Server 7.0 database backup on SQL Server 2000

Properties

Article ID: 837938 - Last Review: March 19, 2007 - Revision: 1.4
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbbackup kberrmsg kbprb KB837938

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com