Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 High Availability (2008)
 Mirroring going away in favor of Always On?

Author  Topic 

aspeckman
Starting Member

10 Posts

Posted - 2013-09-18 : 11:20:46
I heard that Database Mirroring is going away in SQL Server and Availability groups will be used instead.

My only issue with that is right now Traditional Mirroring doesn't require a cluster. Clusters require domain controller permissions for the Machine accounts($machinename) to create cluster name objects in AD.

If you don't have any control over your domain, and the DC is centrally managed with a huge bureaucratic process to get things done by less-than-qualified Domain Admins, then if we want to use Mirroring for HA, we HAVE to be dependent, on a project basis, with another group to implement clustering as part of Availability Groups.

I would hate to see mirroring go away for this reason.

Can anyone confirm that Database Mirroring is going away, say in 2014 version.....or whatever.

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2013-09-18 : 11:28:40
See "High availability" and "Database mirroring" here http://technet.microsoft.com/en-us/library/ms143729.aspx



Microsoft SQL Server MVP, MCT, MCSE, MCSA, MCP, MCITP, MCTS, MCDBA
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2013-09-18 : 14:49:41
Once deprecation is announced for a feature, it is there for that version and the next version. Deprecation for mirroring was announced in 2012, so it should still be available in 2014.

Your concerns are valid. I think we'll see some changes with AlwaysOn in 2014 or in the version afterwards that will address some of the shortcomings of AlwaysOn.

AlwaysOn is a very powerful and flexible feature. We are using it for our most critical application. We've got a 6-node cluster, 3 nodes at the primary site and 3 nodes at the DR site. The 3 nodes at the primary site are synchronous replicas. One secondary synchronous replica is read-intent, the other is a hot standby. The 3 nodes at the DR sites are not participating in the cluster's quorum votes and thus are using node majority for quorum. It is a fairly complex setup and suits the needs of this application. However, it does not suit the needs of most of our other database, so we are using traditional database mirroring for those.


Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page
   

- Advertisement -