October 4, 2012 at 6:51 am
hi,
I road that artical about HA for SQL environment. it is good informations.
In ideal environment, it is very important and well recommended to keep the subscriber, publisher and distributor in a separate physical hardware set up.
Central publisher, central subscriber, and publishing subscriber are the most popular replication topologies used today.
I am not familiar with replication topology; generally for all type of replication configuration required two physical servers. 1. Primary, 2. Secondary server
For creating central publisher and subscriber will need to require one more physical server?
So totally three server or only two servers
1.If we go for merge replication type conflict table will create automatically in primary database.
2.If we go for Transactional replication type will all table should be required primary key in primary database, so existing database cannot configure this replication type.
Thanks
ananda
October 4, 2012 at 7:50 am
In a typical replication topology the Publisher and Subscriber are separate physical machines, probably with large distances between them.
You can integrate the Publisher and Distributor on the same instance but there are, or at least can be, performance ramifications to this especially with a large and busy Publication that has multiple Subscribers.
A lot of thought needs to go into the design of your Replication system, it's certainly the most complicated to design, implement and manage of all the SQL Server HA options
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply