If you allow users write access to replicated tables on the subscriber, you can run into cases where a record is inserted on the wrong server - which will result in a replication stopping error if the same primary key is later inserted on the publisher. Find out how to fix it without pushing a new snapshot.   Read more...

Replicating continuously minimizes latency, but at a cost. If you're replicated a lot of databases, read this article for some ideas about how to trade latency for overhead by runnig your agents in non-continous mode.   Read more...

If you allow users write access to replicated tables on the subscriber, you can run into cases where a record is inserted on the wrong server - which will result in a replication stopping error if the same primary key is later inserted on the publisher. Find out how to fix it without pushing a new snapshot.   Read more...

Need to make changes to table that is an article in a publication? Read this article to get step by step instructions on how to do it without doing a new snapshot!   Read more...