Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I would like to seek your advice in designing a high availability architecture at my current work place.

We are moving to SQL Server 2012 platform and we currently have a set of OLTP databases serving for the application usage and these databases are being replicated (transactional, every 3 min) to another box for reporting purposes, I'm thinking of replacing replication with SQL Server 2012 High availability groups (asynchronous) (one of the reasons to bring high availability groups in to picture is to have HA in cases like database corruption (ex: page level corruption))

Q: as the indexing on report databases is different to indexing on application dB’s, the failover between app db and reporting db will not provide better performance to application or reports on failover, this makes it a bit hard to design an effective cluster.

Please let me know if you can suggest a better solution for this situation.

Appreciate your help.

Cheers, Kiran

share|improve this question
    
With divergent schemas, you would need to have a copy of both production and reporting to use any variant of AlwaysOn because it works at a lower level than Replication does. –  Jon Seigel Mar 18 at 17:12

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.