Article ID: 814579
Article Last Modified on 10/16/2003
APPLIES TO
- Microsoft SQL Server 2000 Standard Edition
- Microsoft SQL Server 7.0 Standard Edition
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:
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:
- Log on to a computer where a SQL Server 7.0 database exists.
- Open SQL Server Enterprise Manager.
- Expand the SQL Server Group, and then click to select <SQL Server_Name>.
- Expand <SQL Server_Name>, and then click to expand the Databases folder.
- Right-click <Database_Name>, and then click Properties.
- 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
Keywords: kberrmsg kbupgrade kbsysadmin kbprb KB814579