Microsoft KB Archive/251628
INF: SQL 7.0 Automatically Rebuilds a Missing LDF File After Restarting SQL Server
The information in this article applies to:
- Microsoft SQL Server version 7.0
SQL version 7.0 rebuilds a new 1 MB physical transaction log file under the following conditions:
- Microsoft SQL Server must be shut down without error prior to deleting the LDF file to ensure consistency in the database.
- SQL Server 7.0 only rebuilds the LDF if it is the PRIMARY log file and the log is not spread over multiple LDF files.
- SQL Server 7.0 rebuilds the user LDF or TEMPDB LDF physical transaction log files if they were deleted or renamed and adds an "unable to activate" entry in the ERRORLOG.
To test this feature, stop SQL Server and rename both the pubs_log.ldf and northwnd_log.ldf files. Restart the server and note that the new LDF files are built in the DATA directory. Also, the following notation is in the errorlog:
SAMPLE ERRORLOG:2000-01-18 09:57:26.71 spid6 Opening file c:\mssql7\DATA\msdblog.ldf. 2000-01-18 09:57:26.72 spid7 File c:\mssql7\DATA\pubs_log.ldf does not exist - unable to activate. 2000-01-18 09:57:26.72 spid7 Attempting to rebuild primary log file for database pubs. 2000-01-18 09:57:26.82 spid7 Creating file C:\MSSQL7\DATA\pubs_log.LDF. 2000-01-18 09:57:26.87 spid8 File C:\MSSQL7\DATA\northwnd.ldf does not exist - unable to activate. 2000-01-18 09:57:26.87 spid8 Attempting to rebuild primary log file for database Northwind. 2000-01-18 09:57:26.99 spid8 Creating file C:\MSSQL7\DATA\Northwind_log.LDF. 2000-01-18 09:57:27.28 spid8 Closing file C:\MSSQL7\DATA\Northwind_log.LDF. 2000-01-18 09:57:27.44 spid8 Opening file C:\MSSQL7\DATA\Northwind_log.LDF. 2000-01-18 09:57:27.44 spid7 Closing file C:\MSSQL7\DATA\pubs_log.LDF. 2000-01-18 09:57:27.47 spid7 Opening file C:\MSSQL7\DATA\pubs_log.LDF.
Additional query words:
Keywords : kbfile kbSQLServ700
Issue type : kbinfo
Technology : kbSQLServSearch kbAudDeveloper kbSQLServ700
Last Reviewed: October 27, 2000