Hi,

We configured a transactional replication and i is working fine.Some started the snapshot agent again and they stopped it in middle.It is completed only 50%.However,log reader agent is running successfully.

As per my knowledge,there would be no issue due to this change.I am not running it again because it will create a burden to our db.

Can someone let me know if there would be any  issue?

It could be things like blocking or the snapshot agent running out of space on disk.

What error message was raised?

It is stopped manually.

I want to keep it like that because it will not impact replication.Please correct me if i am wrong.

Hi Mito

yes if you cancel in half its not an issue. Until unless your subscription expires you dont need snapshot.

To avoid snapshot expiration , please refer publsher prop

Hello Mito - In an ideal scenario Snapshot agent does not need to be started unless you have added new article or you have added new subscriber that needs NEW full snapshot for initialization.

Having said this, even though someone has started it and stopped it mid-way, it is not going to impact the existing Replication topology since Log-reader is independently scanning the T-Log for log records that needs to be moved to Distribution database followed by replaying those by Distribution agent.

However You must note that, you will have to generate new full snapshot in case you wish to add new subscriber since the current one is now invalid

Hope this helps !

What is the status of the distribution agent? Does it say waiting on the snapshot agent to complete? If it does you will need to restart the snapshot agent and let it complete.

If the distribution agent has messages says idle, or is replicating commands you are ok.