We have an OLTP, DSS, and separate Distribution machine. The OLTP serves as
a "HUB" for our 18 server bi-directional replication scenario, and the
replication machine regulates the flow of that "HUB" data. In the event that
our OLTP server becomes non-operational, is anyone familiar with how we could
point multiple remote publishers to the DSS machine without breaking down all
remote publications and subscriptions...we're afraid of the data loss
associated with dropping publications and subscriptions.
Thanks.
Wendy Sporleder
With un-directional replication you can have multiple publishers publishing
to the same subscriber.
If the main publisher went off line a standby publisher could go online and
start replicating to these same subscribers. The number of transactions lost
would be whatever had not made it to the standby server.
With bi-directional replication you would know that all the data is in the
subscriber, and then you would be faced with the same question as to what
data was still in the publisher which has yet to make it to the subscriber.
You would probably be best to do no-sync subscriptions and then validations
to ensure each node is consistent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"wendy.sporleder@.carlson.com"
<wendy.sporleder@.carlson.com@.discussions.microsoft .com> wrote in message
news:FFE2AE1D-7436-402C-9698-140A26A5EFBA@.microsoft.com...
> We have an OLTP, DSS, and separate Distribution machine. The OLTP serves
as
> a "HUB" for our 18 server bi-directional replication scenario, and the
> replication machine regulates the flow of that "HUB" data. In the event
that
> our OLTP server becomes non-operational, is anyone familiar with how we
could
> point multiple remote publishers to the DSS machine without breaking down
all
> remote publications and subscriptions...we're afraid of the data loss
> associated with dropping publications and subscriptions.
> Thanks.
> Wendy Sporleder
>
订阅：
博文评论 (Atom)
没有评论:
发表评论