BUG: Unsuccessfully Renamed User Table Shows in SEM

Last reviewed: May 2, 1997
Article ID: Q140717

The information in this article applies to:

Microsoft SQL Server, version 6.0

BUG# NT: 11990 (6.00)

SYMPTOMS

When the SA or DBO attempts to rename a user-owned table in SQL Enterprise Manager (SEM), the rename fails with an error 15009:

   The object '%s' does not exist in database '%s'

and the table name is not changed in sysobjects. However, the new table name is shown in the EDIT Table/Manage Tables option. If the new table is selected from the drop-down list box, an error 21770 occurs:

   The name '%s' was not found in the specified collection)

WORKAROUND

Impersonate the table owner using SET USER in order to rename the tables.

-or-

Sign on as the user rather than SA or DBO in the user database and rename the tables.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 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 winnt user
Keywords : kbbug6.00 kbtool SSrvEntMan
Version : 6.0
Platform : WINDOWS
Issue type : kberrmsg

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.