No. Of Subscribers in Transactional Replication...

Hi,

I am Using Transactional Replication with Updatable Subscriptions. Is there any limitations in the number of subscribers (Servers) used for this type of replication?

I have a scenario of configuring this replication in 60 Subscribers(Servers). And the replication should be in the Continuous running mode. Will Transactional Replication with Updatable Subscriptions work in this scenario? Or is it meant to work for less than 10 subscribers?

Please reply asap.

Thanks in advance.

Regards,

Swapna.B.

Hi Swapna,

This question has been answered in the following posting.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=754018&SiteID=1

60 subscribers should be fine for transaction replication. However, you should go over the "Considerations for Using Updatable Subscriptions" in following article.

http://msdn2.microsoft.com/en-us/library/ms151718.aspx

Gary

|||

Hi Gary,

Thanks a lot.

Regards,

Swapna.B.

No sync subscriptions

I have a 70 GB merge-replicated production database on which I need to
perform some maintenance. This maintenance will require the removal of my
subscription. I am trying to minimize downtime, obviously, and wonder about
the ramifications, if any, of setting up a no-sync subscription after my
maintenance is complete. The subscription exists off-site, and I want to
avoid a new subscription push across the WAN. Also, I see a snapshot option
to "Keep the existing table unchanged." Would that be better than a no-sync?
In the past, we have always dropped and recreated objects during replication
setup.
Thanks!
Stephanie Williams
Stephanie,
the no-sync option is the way to go. "Keep the existing table unchanged."
is used for a central subscriber topology. The only thing to be wary of is
making sure the data stays synchronized ie can youprevent changes to the
publisher during the subscriber downtime?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)