January 16, 2014 at 11:59 am
We implemented entrust identity guard and THEIR advice was to use transaction replication to set another database on another server that it can use to fail over to if needed. You specify two servers in their connection string, and it will try the second server if it can't get to the first.
My question is this...
Is this the best method? It seems this is a terrible idea. For example, if it can't reach the 1st server, it will fail over to the replicated server and write some data... if it does this, won't I need to backup the replicated DB and restore it back to the original? Wouldn't mirroring be better? Or merge replication?
January 17, 2014 at 3:32 am
Are you keeping 2nd server idle? i.e. no read/wirte on the 2nd server and need High Availability than you can think of Database Mirroring. Also DB mirroring give you flexibility to manual/auto faliover.
HTH
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
January 17, 2014 at 3:45 pm
The second server is idle, it will only be used to fail over to by the software IF our Entrust cannot hit the main SQL box..so users can always authenticate. Why wouldn't they suggest mirroring? Instead they say replication, replication, etc..
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply