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.
SQL Server 2005 stops and then restarts unexpectedly. When you examine the SQL Server 2005 error log file, you find that errors have occurred in the tempdb database. The error messages resemble the following:
DateTimeSPID Error: 602, Severity: 21, State: 30.
DateTimeSPID Could not find an entry for table or index with partition ID 491897996509184 in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
DateTimeSPID Error: 9001, Severity: 21, State: 5.
DateTimeSPID The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
DateTimeSPID Error: 3449, Severity: 21, State: 1.
DateTimeSPID SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
To resolve this problem, obtain Cumulative Update 3 for SQL Server 2005 Service Pack 2 (build 3186).
For more information about how to obtain Cumulative Update 3 for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative update package 3 for SQL Server 2005 Service Pack 2
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 do not have to restart the computer after you apply this hotfix.
You do not have to change the registry.
Hotfix file information
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.