Replication for performance
-
Hi,
I have a database that is used in two countries A and B.
The database (DB) is now in country A, so general use from country B is not offering a good performance.
I am thinking in implement a replication schema, with two identycal databases DBA and DBB, where each server is publisher and subscriber of all tables in the database (transactional immediate with no subscription updates allowed)
I think that doing it that way, I avoid possible conflicts (there's no way by the moment to partition the data, and I need to make updates in both countries)
What do you think of that solution?
Will updates be very slow? Will SQL Server process local and remote changes synchonously or P2C is made asynchronouly?
Thanks in advance, any help would be very appreciated
Alfredo
-
A merge publication can be updated at two or more locations and could be the answer to your problem. Your applications will need to support it though.
-
inmediate updating would be slow.
The update would be commited in both server at the same time, and if you hace a slow net then you could have problems, causing the entire transaction to be rollbacked in both servers.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply