FIX: Primary Key Can Be Dropped if Table is Published

Article translations Article translations
Article ID: 247492 - View products that this article applies to.
This article was previously published under Q247492
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56582 (SQLBUG_70)
Expand all | Collapse all

SYMPTOMS

Publishing a table for transactional replication relies on a primary key constraint being created on that table. However, after replication has been set up, it is possible to drop the constraint. This should not be allowed and it results in the logreader task failing with the following errors displayed in the logreader log:
Publisher: {call sp_replcmds (500)}
Status: 0, code: 0, text: 'The process could not execute 'sp_replcmds' on '%s'.'.
The process could not execute 'sp_replcmds' on '%s'.
Status: 0, code: 18756, text: 'Could not get replication information for table %d'.

WORKAROUND

To work around this problem, do not alter or drop the primary key constraint for a table that is published for transactional replication. If the primary key for a table must be altered, the table must be unpublished and then re-published.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 247492 - Last Review: October 22, 2013 - Revision: 2.1
APPLIES TO
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB247492

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com