FIX: Permission Denied Error 229 Updating Table with DBID>10

Last reviewed: April 9, 1997
Article ID: Q158808
The information in this article applies to:
  • Microsoft SQL Server, version 6.5

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:

  1. Non-SA user runs stored procedure A.

  2. Stored procedure A calls procedure B.

  3. Procedure B updates a table through a cursor in which the table is located in another database.

  4. The other database must have a DBID greater then 10.

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.

Additional Reference Words:


Keywords : kbbug6.50 kbfix6.50.sp2 kbusage SSrvStProc
Version : 6.5
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.