I have a publisher with a stable internet connection. I have a subscriber with a very unstable internet connection. It drops randomly and I need to have the replication work when it comes back up without reinitializing subscriptions.
But it seems like I keep having to reinitialize all subscriptions in order for the replication to start back up. Then it gets part of the way threw and restarts, likely due to the internet connection dropping. It takes me several minutes to get everything back down to the subscriber and my ap is offline during this time. And if the internet connection drops I have no way of telling my users how long it will be offline. I'm totally at the mercy of the internet connection. When the replication stops at least I have most of the data, but once I reinitialize all subscriptions my tables are wiped out and the ap is completely offline until it finishes. This is because it is moving all these large tables again and not just the changing transactions. How do I get around this?
These two lines are what I see in replication monitor when the replication appears to not be working. ie. someone has entered something at the publisher and I don't see it at the subscriber.
**No Replicated Transactions Are available
This is the error that comes up part way threw the replication when the connection is dropped...
**TCP Provider: An existing connection was forcibly closed by the remote host.
Then the replication restarts again....unless the whole table got copied in that case it skips that table.
Thanks in advance for your help.