BUG: SQL Object Manager Not Allow Foreign Key on Same Table

Last reviewed: April 30, 1997
Article ID: Q121238

The information in this article applies to:

  - Microsoft SQL Server version 4.21

BUG# 10177 (4.21)

SYMPTOMS

The Microsoft SQL Object Manager does not allow a foreign key to be defined on the same table as the primary key.

The Keys dialog of Object Manager does not list the server chosen in the pick box to match a foreign key, so you cannot create a foreign key against the same table as the primary key.

WORKAROUND

Use the sp_foreignkey stored procedure to accomplish this objective.

STATUS

Microsoft has confirmed this to be a problem in SQL Object Manager for Windows NT and SQL Object Manager for Windows. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words:
Keywords : kbbug4.21 kbtool SSrvObj_Man SSrvWinNT
Version : 4.21
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 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.