March 24, 2009 at 3:01 pm
I need some adivce on replication. I have 4 servers that have the same database on them. I would like to replicate a few tables on each of the server whenever either one of them encounters a change. What would be the best method to solve this problem. Thanks in advance....
March 24, 2009 at 7:17 pm
updatable subscriber transactional replication
i think it adds a guid column to your table so test in QA. an ex-dba did it here and it crashed the main app because it does a select * in that table and the extra column the code couldn't handle it
March 25, 2009 at 12:52 pm
Although peer-to-peer can potentially work you should avoid multiple writers because conflict resolution can become a problem.
Merge was designed for that but it is very intrusive with the schema. If you must be able to change every where and you can handle the administrative load, Merge is probably the way to go!
* Noel
March 25, 2009 at 3:40 pm
I am using SQL 2005 so i have the option of Database mirroring. Do you think that is a valid option in my scenario. Thanks in advance
March 26, 2009 at 3:49 pm
It is my understanding that the mirrored database is for failover only and is not viewable in anyway. Is this what you need from your replicated databases?
March 26, 2009 at 3:53 pm
I need realtime syncronization. All database will be functional at all times. So im guess transactional replication is the more appropriate solution.
March 26, 2009 at 4:05 pm
Vijay,
Is this an online store scenario, where you have a product catalog and need to keep track of orders or something of that nature?
March 26, 2009 at 4:13 pm
Sort of. We have to syncronize Inventory data on 4 seperate servers (located at 4 seperate site but within the same domain) which have the same database.
March 26, 2009 at 4:34 pm
If you have the option to do some redesign of the application you might want to try something like:
Reading from your Inventory table, but updating your InventoryUpdate View that uses 4 part naming to update a master inventory table on another server. Then that table replicates back forward to your inventory tables on all 4 servers.
Just an idea, and it would minumize your replcation headaches.
March 30, 2009 at 12:43 pm
Michael Wood (3/26/2009)
If you have the option to do some redesign of the application you might want to try something like:Reading from your Inventory table, but updating your InventoryUpdate View that uses 4 part naming to update a master inventory table on another server. Then that table replicates back forward to your inventory tables on all 4 servers.
Just an idea, and it would minumize your replcation headaches.
Excellent suggestion!
* Noel
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply