A employee of mine pointed out this quote from an SQL webpage

“HADR” is a high-availability and disaster recovery solution introduced in SQL Server Code-Named “Denali” to enable you to maximize availability for one or more of your user databases. Deploying “HADR” involves configuring one or more availability groups. Each availability group establishes the context within which a selected set of user databases can fail over as a single unit.

The availability group involves a set of failover partners, known as availability replicas. Each availability replica possesses a local copy of each of the databases in the availability group. One of these replicas, known as primary replica, maintains the primary copy of each database. The primary replica makes these databases, known as primary databases, available to users for read-write access. For each primary database, another availability replica, known as a secondary replica, maintains a failover copy of the database known as a secondary database.

http://msdn.microsoft.com/en-us/library/ff877884(SQL.110).aspx

along with the comment – “so SQL are going down the DAG path”….

Wouldn’t it be nice to actually see the product teams at MS talk and utilise some common technology between products.

this ofcourse could be seen as the first step to long talked about merging of the exchange ese database into using SQL as the backend.

On a slightly related note – I’ve been pretty happy with Lync 2010. Its use of replica databases on every server is a good move. The OCS product range has finally hit maturity – and while its not perfect, the product has got to the point where not only is it functionally good – but its reasonably good to admin, the client is finally pretty polished – and the all round experience is quite impressive.