edit
I'm testing possible solutions for database redundancy and high availability,I tested mirroring it worked fine, but lacks scalability plus there will be a lot of work in one server. Now I discovered Merge Replication, and in paper looks great (although I still need to know what happens if a server goes down and them comes alive again, will it synchronize? can you answer me to this one too?)
edit
My objective is to have various applications working simultaneous and communicating with one database only. But having the databases synchronized between them and that in case of one database goes down, all its data is not lost.
Is it possible to do this with Merge Replication?? where all sql instances are both publishers and subscribers, and have an distributor inside them.
Any considerations I should take, or other possible solutions for my problem?
regards
Best Answer
You can do it with SQL replication, but in my experience it is an exotic and somewhat problematic technology.
Are your server's geographically separated? What is the need for having 3 copies of the data?