Hi Friends,
I have asked this question earlier, but did not get a reply that I would suffice with... so asking it again
My Customer is revamping his server setup, the design he wants is something like this
Two copies of the same database on 2 different servers, both should be in sync every time and at the same time he wants that both the databases should be available for read/write operations... and this should be a DR setup, i.e. if one goes down the other should take the load.
I though of using replication ... peer to peer OR Merge OR Transactional replication with updateable subscriptions.
Peer to Peer : As It is capable of being implemented as a DR solution I though this would be ideal, but I am discarding this as I have read in many articles that there are synchronization issues for conflicting rows and it throws an error message on finding such conflicts.
Merge replication OR Transactional replication with updateable subscriptions : can I use one of these.
Also I want to know .. how advisable (or rather foolish) is it to use Replication (any setup) for a 5GB database which should have a latency of not more than 1 min.
OR should I scrap this idea of replicating and use always on.. where in I can use the secondary node or reporting at least.
For this I may need to convince the customer.