BUG: Cross-Database Table Creation/Drop in Stored Procedure

Last reviewed: May 2, 1997
Article ID: Q148224

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 13656 (6.00)

SYMPTOMS

After the database owner (dbo) of a database creates a stored procedure that creates a table in another database, inserts data into the table, selects from the table, and then drops it, the dbo then grants execute permission on this procedure to a user who is a user in both databases. When the user executes the procedure, it executes fine the first time, but on the second time and each time thereafter, the user gets the following error messages:

   Msg 2714, Level 16, State 1
   There is already an object named 'tblname' in the database.
   Msg 267, Level 16, State 1
   Object '' cannot be found.

WORKAROUND

Use the WITH RECOMPILE option to either create or execute the procedure.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: sql6
Keywords : kbbug6.00 kbusage SSrvGen SSrvProg
Version : 6.0
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: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.