FIX: Permission Denied Error 229 Updating Table in Another DB (157847)
The information in this article applies to:
This article was previously published under Q157847
BUG #: 16107 (6.50)
SYMPTOMS
A non-system administrator (SA) user will receive a Permission Denied error
message (number 229) when he or she tries to update a table through a
stored procedure, even if the user has permission to run the stored
procedure. If the SA or database owner (DBO) runs the stored procedure
first, the user will then be able to use the stored procedure. This problem
occurs when the following sequence of events occurs:
- Non-SA user runs stored procedure A.
- Stored procedure A calls procedure B.
- Procedure B updates a table through a cursor in which the table is
located in another database.
WORKAROUND
To work around this problem, do one of the following:
- Do not use cursors to update tables when the cursor is in a stored
procedure that is called by another procedure.
- Give the user permissions to the underlying table.
- Have the DBO run all stored procedures affected by this problem every
time SQL Server is restarted. This allows normal users to run the stored
procedures.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 6.5. This problem has been corrected in U.S. Service Pack 2 for
Microsoft SQL Server version 6.5. For more information, contact your
primary support provider.
Modification Type: | Major | Last Reviewed: | 10/3/2003 |
---|
Keywords: | kbBug kbfix kbnetwork KB157847 |
---|
|