INF: Sp_fkeys Does Not List Keys Identified by Sp_foreignkey

Last reviewed: May 28, 1997
Article ID: Q169051

The information in this article applies to:

Microsoft SQL Server, versions 6.0 and 6.5

SUMMARY

The sp_fkey stored procedure only returns information about columns explicitly defined by ALTER TABLE or CREATE TABLE with a FOREIGN KEY constraint, and not for columns identified by sp_foreignkey. The sp_foreignkey stored procedure was last supported in SQL Server 4.21a, and is only provided for backwards compatibility with later systems. The use of sp_foreignkey was made unnecessary with the implementation of declarative referential integrity (DRI) in SQL Server 6.0.

MORE INFORMATION

For more detailed information, see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q133177
   TITLE     : INF: Changes to SQL Server 6.0 That May Affect 4.2x Apps

Also see the ALTER TABLE command in the Transact-SQL Reference 6.0 and the ALTER TABLE command in What's New in SQL Server 6.5.

Additional query words: sp_fkeys
Keywords : kbusage SSrvGen
Version : 6.0 6.5
Platform : WINDOWS
Issue type : kbinfo

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 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.