Article ID: 922804
Article Last Modified on 11/20/2007
APPLIES TO
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Express Edition with Advanced Services
BUG #: 442810 (SQLBUDT)
BUG #: 1057 (SQL Hotfix)
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.
SUMMARY
This article describes the following about this hotfix release:
- The issues that are fixed by this hotfix package
- The prerequisites for applying this hotfix package
- Information about whether you must restart the computer after you apply this hotfix package
- Information about whether this hotfix package is replaced by any other hotfix package
- The files that are contained in this hotfix package
SYMPTOMS
After you detach a Microsoft SQL Server 2005 database that resides on network-attached storage, you cannot reattach the SQL Server database. Additionally, a message that resembles the following may be logged in the Application log:
CAUSE
This problem occurs because SQL Server 2005 resets the file permissions when the database is detached. When you try to reattach the database, it cannot be attached because of limited share permissions.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005
Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
There are no prerequisites for this hotfix.
Restart information
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix is not replaced by any other hotfixes.
File information
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.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Logread.exe | 2005.90.1551.0 | 397,088 | 19-Jul-2006 | 23:40 | Not Applicable |
| Microsoft.sqlserver.replication.dll | 2005.90.1551.0 | 1,608,480 | 19-Jul-2006 | 23:36 | Not Applicable |
| Microsoft.sqlserver.smo.dll | 9.0.1551.0 | 1,559,328 | 19-Jul-2006 | 23:36 | Not Applicable |
| Microsoft.sqlserver.sqlenum.dll | 9.0.1551.0 | 895,776 | 19-Jul-2006 | 23:36 | Not Applicable |
| Osql.exe | 2005.90.1551.0 | 51,488 | 19-Jul-2006 | 23:35 | Not Applicable |
| Replrec.dll | 2005.90.1551.0 | 781,088 | 19-Jul-2006 | 23:35 | Not Applicable |
| Msmdlocal.dll | 9.0.1551.0 | 15,626,528 | 19-Jul-2006 | 23:37 | Not Applicable |
| Msmdredir_dll | 9.0.1551.0 | 3,929,888 | 19-Jul-2006 | 23:37 | Not Applicable |
| Sqlaccess.dll | 2005.90.1551.0 | 349,472 | 19-Jul-2006 | 23:40 | Not Applicable |
| Sqldiag.exe | 2005.90.1551.0 | 960,288 | 19-Jul-2006 | 23:36 | Not Applicable |
| Sqlservr.exe | 2005.90.1551.0 | 28,791,128 | 19-Jul-2006 | 23:37 | Not Applicable |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 2.
MORE INFORMATION
To change the behavior in SQL Server 2005 after you apply this hotfix, follow these steps:
- Use the -T startup option to start SQL Server. Use this startup option to turn on trace flag 1802 in SQL Server Configuration Manager. For more information about how to change the startup parameters, visit the following Microsoft Developer Network (MSDN) Web site:
Use the following command to detach the database.
exec sp_detach_db DatabaseName go
Use the following command to reattach the database.
exec sp_attach_db DatabaseName, '\\Network-attached storage_Path\DatabaseMDFFile.mdf', '\\Network-attached storage_Path\DatabaseLDFFile.ldf' go
Keywords: kbtshoot kbfix kbqfe kbpubtypekc kbhotfixserver kbsql2005engine kbsql2005sp2fix KB922804
