Hi Gail,

Thank you for your response and suggestions, we may well end up doing something like this. Another option would be for us to break the SQL Agent into two separate jobs (one scheduled after the other), although this just means more maintenance going forwards and is not particularly attractive as a solution.

Is there definitely no T-SQL way of pushing all outstanding changes across, or manually calling the replication process (even though it runs continuously)? It would be great if we could run a job step to ensure that known changes are replicated at the subscriber before a subsequent SQL Agent job step is executed.