You should not ever run sp_replrestart. That is an internal stored proc which is used in by the system.
sp_replrestart has reset the current pointer to say everything was delivered. The only way to fix this now, is to reinit the subscription.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
One morning; got message from one of the replicated locations (target database) that latest entries aren't seen (from source database); found that message was prompted as 'could not execute sp_replcmds'. After checking; fired the command as 'sp_replrestart' to start replication; after it replication started and latest entries got synced; however the entries from start of issue of 'could not execute sp_replcmds' until firing of sp_replrestart did not got replicated to target database.
Can this situation be avoided. Also, is there a way whereby; the entries from start of this message until replication restart do not get skipped and get synced to target database. Thanks in advance.
You should not ever run sp_replrestart. That is an internal stored proc which is used in by the system.
sp_replrestart has reset the current pointer to say everything was delivered. The only way to fix this now, is to reinit the subscription.
Hi @DM ,
Please see this similar thread: https://stackoverflow.com/questions/2723061/sql-server-2008-replication-failing-with-process-could-not-execute-sp-replcmds
And this: https://www.dcac.com/sql/the-process-could-not-execute-sp_replcmds-on/
Best regards,
Seeya
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.