Hi,
We currently have a clustering setup for our SQL 2008 that works well. We have however decided to move up to SQL 2012, and the consultant advised to sstart using AlwaysOn High Availability.
We have however been running into issues like :
- The sql jobs that has to be changed to look whether a server is primary.
- Replication is an issue so we had to setup another server as a distribution agent.
- Reporting Services jobs (not sure how to handle this yet)
- Worries about speed for synchronous as we have a production database with high load of transactions
So at this stage we are really unsure about continuing on this route and maybe just rather use disk clustering again.
The reasons our administrator is saying we should go High Availibility is :
- More memory available to SQL Server
- Faster failover
- Easier administration.
So we are not sure what to do at this stage, but we aren't getting a good feeling regarding High Availability.
Thanks