BUG: Snapshot Replication Requires Primary Key Constraint

Last reviewed: April 9, 1997
Article ID: Q160869

The information in this article applies to:

Microsoft SQL Server, version 6.5

BUG #: 12252 (NT)

SYMPTOMS

The "Snapshot Replication" section in Part Three, "What's New for Administrators," of the "What's New for SQL Server 6.5" guide states the following:

   To enable snapshot replication to tables without primary keys, run the
   sp_addarticle stored procedure to create the articles; the table names
   will not appear in the Article Table list if they do not have a declared
   primary key.

However, the stored procedure, sp_addarticle, only allows "log based" types of articles to be created (which require a primary key to exist on the table).

WORKAROUND

Create a primary key constraint on any table to be published.

STATUS

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

Additional query words: publication
Keywords : kbbug6.50 SSrvDoc_Err
Version : 6.5
Platform : WINDOWS
Issue type : kbdocerr

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.