Hi, does anyone have experienc implementing always on feature of the sql server 2012. I am bit confused,and left me with few questions. 1) Is this a better version of the replication feature of 2008 or mirroring OF SQL SERVER 2008. 2) What is the hardware requirement for implementing this feature. i.e Even implementing native mirroring or replication of the datbabases of sql server do we need to have approved clustering hardware from MICROSOFT? This is important to understand as one of our consultants is advising to purchasing sql server 2012 for using this feature, where as all we are trying to plan is replication of few databases. thanks!
1) I would compare it to mirroring on steroids. You get the basic functionality of mirroring with multiple secondaries, read only secondaries, and a single connection point at the listener so that you don't have to write special app code to deal with failovers. It's a pretty slick set of technology. It's not based off replication at all. 2) You must have servers in a cluster, but they do not have to be matching hardware, no longer require shared disks, in fact, the requirements are pretty slack on a hardware standpoint. You do have to have SQL Server Enterprise running, so the minimums there apply, but other than that, I'm not aware of much else that you have to do hardware-wise. It's primarily a software solution and not a hardware/software solution like the old clustering environments. There is no approved hardware list that I'm aware of. Keep an eye on
brentozar.com. He's due to publish an article about a major implementation of Availability Groups and the headaches he ran into. But the basic technology is functional and the lack of shared resources makes possible all kinds of wonderful opportunities such as remote site failover and all sorts of other things along those lines.