Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
If you are a Small Business customer, find additional troubleshooting and learning resources at the Support for Small Business site.
When you try to restore a transaction log for a Microsoft SQL Server 2005 database, you may receive error 3456. When this error occurs, you cannot continue restoring the transaction log.
Additionally, when you examine the SQL Server Errorlog file, it resembles the following:
2007-03-29 16:00:35.43 spid59 Error: 17053, Severity: 16, State: 1.
2007-03-29 16:00:35.43 spid59 G:\MSSQL\DATA\attach_space_079.ndf: Operating system error 112(There is not enough space on the disk.) encountered.
2007-03-29 16:00:35.45 spid59 Error: 5149, Severity: 16, State: 1.
2007-03-29 16:00:35.45 spid59 MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file.
2007-04-14 13:11:58.82 spid56 Error: 3456, Severity: 16, State: 1.
2007-04-14 13:11:58.82 spid56 Could not redo log record (509687:1091266:3), for transaction ID (0:84708793), on page (67:57769216), database 'custdata' (database ID 7). Page: LSN = (508062:635535:172), type = 8. Log: OpCode = 7, context 8, PrevPageLSN: (509687:1090182:20). Restore from a backup of the database, or repair the database.
This problem occurs when you receive errors 17053 and 5149 before you try to restore the transaction log. Errors 17053 and 5149 occur when error 112 occurs. Error 112 occurs because there is not enough space on the disk.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
How to obtain the latest service pack for SQL Server 2005
You have to restart the computer only if all SQL Server components are not shut down before you install this hotfix. The hotfix installer will inform you of any running SQL Server components that must be shut down so that you can shut down them to avoid a system restart.
Hotfix replacement information
This hotfix is not replaced by any other hotfixes.
You do not have to change the registry.
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.