BUG: Primary Key Can Be Dropped if Table is Published

• Microsoft SQL Server version 7.0

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 version 7.0.

Additional query words:

Keywords : SSrvDRI SSrvRep kbbug7.00 kbSQLServ700bug
Version : winnt:7.0
Platform : winnt
Issue type : kbbug