July 8, 2004 at 8:52 pm
Hi .. I have 2 servers A and B. Server A being a Live server running an application with MS SQL 2000 and Server B being a backup server. I would like to replicate the databases from server A to B daily. And should server A be shut down or fails, users will access the application from Server B with the latest replicated database.
May I know which replication (Transaction or Merge) suits the above scenario?
It will be most likely a 1 way replication from server A (Publisher) to server B (Subscriber) and shd it be a Push or Pull replication?
Appreciate all comments and advices
Thank You
July 9, 2004 at 1:15 am
In your Scenario, If ServerA does go down how will the Applications connect to the ServerB?
Replication is not normally used for Failover support. Not unless you can painlessly get your Applications talking to the ServerB. Then you have to think about syncronising data between Databases when you have brought up ServerA again.
July 9, 2004 at 2:04 am
Hi thx for the reply, to ans ur query, Server B will have the application installed pointing to server B's database at this moment. Thus even if server A is down, the applications will automatically be pointing to server B painlessly.
Back to the earlier posting, any recommendations to which replications to use?
July 9, 2004 at 2:35 am
It sort of depends on latency and data loss acceptablity.
If both servers are on site and the network has enough bandwidth then I would say go transaction repl.
But here is the other thought, look at clustering - either Active/Active or Active/Passive. Most applications can handle it with just disconnect and reconnect.
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply