Article ID: 913941
Article Last Modified on 11/20/2007
APPLIES TO
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Express Edition with Advanced Services
- Microsoft SQL Server 2005 Workgroup Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Standard X64 Edition
Bug #: 155 (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.
This article describes the following about this hotfix release:
- The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix package
- Whether you must restart the computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix package
SYMPTOMS
Consider the following scenario. You create a SQL Server login, and then map a user to the login in a database (Database A). This login does not have permissions to access other databases. You log on to the instance of SQL Server by using the SQL Server login. In this scenario, the SQL Server login may have more permissions than when you created the login. This problem occurs if all the following conditions are true:
- You set the TRUSTWORTHY option for Database A to ON.
- Database A is trusted at server scope. By default, Database A is trusted at server scope because the dbo user is mapped to a member of the sysadmin fixed server role.
- You run a module that is marked as EXECUTE AS '
user_name'. This user is mapped to the sa login. - The module includes a BACKUP statement.
For example, you can perform operations as a member of the sysadmin fixed server role in the execution context of the SQL Server login.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft 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
You must have installed SQL Server 2005 to apply this hotfix.
Restart information
You do not have to restart the computer after you apply this hotfix.
Registry information
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.
SQL Server 2005 32-bit version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Msmdlocal.dll | 9.0.1518.0 | 15,585,496 | 20-Jan-2006 | 09:11 | x86 |
| Msmdredir.dll | 9.0.1518.0 | 3,927,256 | 20-Jan-2006 | 09:11 | x86 |
| Msxmlsql.dll | 2005.90.1518.0 | 899,638 | 20-Jan-2006 | 08:11 | x86 |
| Osql.exe | 2005.90.1518.0 | 51,416 | 20-Jan-2006 | 09:11 | x86 |
| Sqlaccess.dll | 2005.90.1518.0 | 349,400 | 20-Jan-2006 | 09:11 | x86 |
| Sqlservr.exe | 2005.90.1518.0 | 28,778,256 | 20-Jan-2006 | 09:11 | x86 |
SQL Server 2005 x64-based version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Msmdlocal.dll | 9.0.1518.0 | 15,585,496 | 20-Jan-2006 | 09:11 | x86 |
| Msmdredir.dll | 9.0.1518.0 | 3,927,256 | 20-Jan-2006 | 09:11 | x86 |
| Osql.exe | 2005.90.1518.0 | 83,672 | 20-Jan-2006 | 13:14 | x64 |
| Sqlaccess.dll | 2005.90.1518.0 | 356,568 | 20-Jan-2006 | 13:14 | x86 |
| Sqlservr.exe | 2005.90.1518.0 | 39,397,592 | 20-Jan-2006 | 13:14 | x64 |
SQL Server 2005 Itanium architecture version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Msmdlocal.dll | 9.0.1518.0 | 48,416,984 | 20-Jan-2006 | 12:30 | IA-64 |
| Msmdredir.dll | 9.0.1518.0 | 6,072,536 | 20-Jan-2006 | 12:31 | IA-64 |
| Osql.exe | 2005.90.1518.0 | 123,096 | 20-Jan-2006 | 12:30 | IA-64 |
| Sqlaccess.dll | 2005.90.1518.0 | 351,448 | 20-Jan-2006 | 12:30 | x86 |
| Sqlservr.exe | 2005.90.1518.0 | 72,181,976 | 20-Jan-2006 | 12:31 | IA-64 |
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
WORKAROUND
To work around this problem, restart the SQL Server service.
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 1.
REFERENCES
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about the EXECUTE AS clause, see the following topics in SQL Server 2005 Books Online:
- TRUSTWORTHY database property
- ALTER DATABASE (Transact-SQL)
- EXECUTE AS Clause (Transact-SQL)
- Extending database impersonation by using EXECUTE AS
Keywords: kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver kbsql2005engine kbsql2005presp1fix KB913941
