zoggling (12/22/2014)
Is there definitely no T-SQL way of pushing all outstanding changes across,
As I said, you can drop the subscriber and re-snapshot. That'll do what you want....
or manually calling the replication process (even though it runs continuously)?
How would calling something that runs *continuously* help? It already runs continuously. Replication latency is a factor of the network and the disks mostly.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability