msrepl_transactions without references to msrepl_commands

If I understand your question correctly - you have data
in msrepl_transactions which doesn't correspond to data
in msrepl_commands. Possibly these rows refer to other
databases where the publications have been removed. The
procedure sp_MSdelete_publisherdb_trans is used by the
cleanup agent and I have seen cases where orphaned
records are left in the transactions table after a
publication has been removed.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
thanks.
can I use: sp_repldone with xact_id to kill these rows?
Regards Thomas
On Mon, 21 Feb 2005 02:13:16 -0800, "Paul Ibiso"
<Paul.Ibison@.Pygmalion.Com> wrote:

>If I understand your question correctly - you have data
>in msrepl_transactions which doesn't correspond to data
>in msrepl_commands. Possibly these rows refer to other
>databases where the publications have been removed. The
>procedure sp_MSdelete_publisherdb_trans is used by the
>cleanup agent and I have seen cases where orphaned
>records are left in the transactions table after a
>publication has been removed.
>Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
|||sp_repldone is related to the transaction log and the log
reader agent, and not really data that has laready
reached the distribution database. If the distribution
cleanup agent doesn't remove the extra transaction
records then I think you'll just have to leave them
there. If there is a huge amount, then contact PSS and
they'll hold your hand while you delete them.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)