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

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

SYMPTOMS

When you back up a SQL Server 7.0 database, and you then restore the database on SQL Server 2000, the restoration process might fail, and you receive the following error message:

Microsoft SQL-DMO (ODBC SQL State: 42000)
The log file for database '<Database Name>' is full. Back up the transaction log for the database to free up some log space.
RESTORE DATABASE is terminating abnormally.
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.
Database '<Database Name>' running the upgrade step from version 527 to version 528.
Database '<Database Name>' running the upgrade step from version 528 to version 529.
Database '<Database Name>' running the upgrade step from version 529 to version 530.
Database '<Database Name>' running the upgrade step from version 530 to version 531.
Database '<Database Name>' running the upgrade step from version 531 to version 532.
Database '<Database Name>' running the upgrade step from version 532 to version 533.
Database '<Database Name>' running the upgrade step from version 533 to version 534.
Database '<Database Name>' running the upgrade step from version 534 to version 535.
Database '<Database Name>' running the upgrade step from version 535 to version 536.
Database '<Database Name>' running the upgrade step from version 536 to version 537.

CAUSE

This behavior may occur when the auto grow option for a transaction log is disabled for the SQL Server 7.0 database that was backed up.

WORKAROUND

To work around this problem, enable the auto grow option of the transaction log file on SQL Server 7.0 before you perform the backup. To enable the auto grow option for the transaction log, use these steps:
  1. Log on to a computer where a SQL Server 7.0 database exists.
  2. Open SQL Server Enterprise Manager.
  3. Expand the SQL Server Group, and then click to select <SQL Server_Name>.
  4. Expand <SQL Server_Name>, and then click to expand the Databases folder.
  5. Right-click <Database_Name>, and then click Properties.
  6. Click the Transaction Log tab. Under the File Properties section, click to select Automatically grow file, and then click OK.

After you enable the auto grow option for the transaction log file on SQL Server 7.0, perform the backup of the database, and then restore it on a SQL Server 2000 server.

REFERENCES

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
317375 INF: Transaction Log Grows Unexpectedly or Becomes Full on SQL Server

Properties

Article ID: 814579 - Last Review: October 16, 2003 - Revision: 3.3
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbupgrade kbsysadmin kberrmsg kbprb KB814579

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