February 3, 2010 at 7:09 am
I going to configure the Replication b't 2 servers which are in SQL 2005, both are placed in different locations. The objective is a set of people from location A is using the server S_A and set of people from B using the server S_B. Everyday nite the data from S_A should be moved to S_B and vice versa. So that I can get the consolidated report whenever I launch the report.
Can anyone pls suggest the replication method which I need to use.
February 3, 2010 at 12:30 pm
Try looking up on Merge replication and see of that will suit your business needs.
-Roy
February 3, 2010 at 9:56 pm
If I Configure the Merge Replication, it adds a Unique Identifier column to all the Tables. Is there any way to avoid this? My concern is it should not affect the existing application.
February 4, 2010 at 6:13 am
Sorry Sheik, I am not an expert in Merge replication. The only other replication that could help you is Peer to Peer. But I am not sure if it will help you.
-Roy
February 4, 2010 at 7:40 am
No Probs. Peer to Peer Replication means "Transactional publication with updatable subscriptions". As I am new to this I dont know about the Peer to Peer method. Can any one suggest....
February 4, 2010 at 8:08 am
In Peer to peer replication each node acts as a publisher and distributor. When a change is made in any one of the nodes, the changes are propagated by the replication to the other nodes.
-Roy
February 6, 2010 at 6:14 am
You mean, in both nodes i should configure the transaction replication?
February 8, 2010 at 12:45 pm
As per books online
Configure distribution at Server A, Server B, and Server C.
Create a publication at Server A by using the New Publication Wizard.
Enable the publication for peer-to-peer replication by using the Publication Properties - <Publication> dialog box.
Initialize the schema and data at Server B and Server C manually or by restoring the database at Server A to Server B and Server C. The schema at all nodes must be identical.
Add Server B and Server C to the topology by using the Configure Peer-to-Peer Topology Wizard. Adding the servers: creates a publication at each server; and creates subscriptions to the publications that are on the other servers in the topology.
If there are any identity columns in published tables, you must reseed the identity ranges for the tables at Server B and Server C.
-Roy
February 12, 2010 at 10:41 pm
In SQL 2k5 the Peer-to-Peer does supports only in Enterprise and Developer Edition. But I have installed Statndard Edition :cool:. I will try this after i install the Enterprise Edition. Otherwise Transaction Replication with updatable subscription only will support for two way comm in Standard Edition.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply