Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sumwanlah
Starting Member
43 Posts |
 Posted - 2002-02-05 : 22:51:17
|
During a transactional replication, what would the publisher/distributor do, if the subscriber goes down? When the subscriber comes back online, and I'm assuming that replication jobs are a must here, would the publisher be smart enough to 'reestablish' the link between itself and the subscriber?I know the bit about committing transactions, so if the subscriber is down, the publisher will not commit any transaction to the subscriber.But does the publisher keep track of what needs to be published? Will there be a 'queue', stemming from uncommitted transactions, that will build-up and take up valuable space?I've got two SQL7 boxes.Actually I kinda like have an answer for this, but because of my still-developing knowledge of replication, my boss is not convinced with my answer... Sheesh! That's why I'm turning to you guys...  I've been like referring to many articles, but most of them never describe situations in detail. |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-02-06 : 11:50:35
|
| The Distributor holds all of the traqnsactions that have not been commited to the subscriber.This data is held in the distribution database. When the subscriber comes back online, the distribution agent will start sending the transactions to the subscriber.-Chad |
 |
|
|
|
|
|
If Subscriber goes down... (Replication)