Hi,

I have a replication setup with master and 2  slaves, lets say if the master database freezes or gets corrupted is there a way switch the master to salve and vice versa automatically to get the database available all times.

Nav

There is nothing called Master and Slave in SQL Server. So if that is your company terminology then we dont know.

If you are reffering about publisher and subsciber, then You cannot change publisher to subscriber or the other way. If you want data to go both ways then you can think of Merge replication or Bi directional transactional replication.

Since you have 3 servers, you can also think of using P2P where all servers are active and work as both publisher and subscriber always.

What replication you are talking about? Master/slave are not the terms we using in MS  SQL replication. MS SQL replication has no option of automatic fail over as it used for different purpose.

But if you are looking for some solution this can be achieved by log shipping or if you are using SQL server 2012 then we can use Alwayson for multiple secondaries. Automatic fail over in case of database corruption can be taken care by these options.