Answered by:
Which is the best DR Solution

Question
-
My Company is going for a SQL upgrade, it would be from SQL Server 2005 to 2012, I have to implement a DR solution. As of now we have Mirroring setup for 2005, for 2012 I am thinking of implanting Always ON. So I want to know which edition of SQL Server 2012 I should be using....
I have 2 Important things to take care
1: Mirroring / ( Always ON)
2: SSIS Packages Migration.
Should I use Enterprise edition
OR
Standard would be sufficient for me..
Please advice
Friday, December 27, 2013 8:28 AM
Answers
-
Only EE support Always On Availability Groups (Mirroring replacement)
Standard Edition supports two node Cluster or you can configure mirroring with FULL safety only...
Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting: Large scale of database and data cleansing
Remote DBA Services: Improves MS SQL Database Performance
SQL Server Integration Services: Business Intelligence
Sunday, December 29, 2013 10:01 AM -
Hi Sudhakar,
As Uri post, SQL Server 2012 Enterprise can support the features of Database mirroring and AlwaysOn Availability Groups. In addition, SQL Server 2012 Standard do not support AlwaysOn Availability Groups, however, it support the feature of AlwaysOn Failover Cluester instances. Deploying AlwaysOn Availability Groups requires a Windows Server Failover Clustering (WSFC) cluster. To be enabled for AlwaysOn Availability Groups, an instance of SQL Server must reside on a WSFC node, and the WSFC cluster and node must be online. The SQL Server 2012 Standard only support two node in the feature of AlwaysOn Failover Cluester instances.
For more information, see:
http://msdn.microsoft.com/en-us/library/cc645993.aspx#High_availabilityFailover Clustering and AlwaysOn Availability Groups (SQL Server): http://technet.microsoft.com/en-us/library/ff929171.aspx
Thanks,
Sofiya LiIf you have any feedback on our support, please click here.
Sofiya Li
TechNet Community SupportMonday, December 30, 2013 3:56 AM
All replies
-
Only EE support Always On Availability Groups (Mirroring replacement)
Standard Edition supports two node Cluster or you can configure mirroring with FULL safety only...
Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting: Large scale of database and data cleansing
Remote DBA Services: Improves MS SQL Database Performance
SQL Server Integration Services: Business Intelligence
Sunday, December 29, 2013 10:01 AM -
Hi Sudhakar,
As Uri post, SQL Server 2012 Enterprise can support the features of Database mirroring and AlwaysOn Availability Groups. In addition, SQL Server 2012 Standard do not support AlwaysOn Availability Groups, however, it support the feature of AlwaysOn Failover Cluester instances. Deploying AlwaysOn Availability Groups requires a Windows Server Failover Clustering (WSFC) cluster. To be enabled for AlwaysOn Availability Groups, an instance of SQL Server must reside on a WSFC node, and the WSFC cluster and node must be online. The SQL Server 2012 Standard only support two node in the feature of AlwaysOn Failover Cluester instances.
For more information, see:
http://msdn.microsoft.com/en-us/library/cc645993.aspx#High_availabilityFailover Clustering and AlwaysOn Availability Groups (SQL Server): http://technet.microsoft.com/en-us/library/ff929171.aspx
Thanks,
Sofiya LiIf you have any feedback on our support, please click here.
Sofiya Li
TechNet Community SupportMonday, December 30, 2013 3:56 AM -
Hi,
Only SQL Server 2012 Enterprise Edition supports AlwaysON.
Thanks and Regards Alankar Chakravorty MCITP Database Administrator SQL Server 2008 MCITP Database Administrator SQL Server 2005
Monday, December 30, 2013 9:36 AM -
Hi
EE supports AlwaysOn Availability Groups, as Std. supports AlwaysOn two node Cluster Instances.
Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting: Large scale of database and data cleansing
Remote DBA Services: Improves MS SQL Database Performance
SQL Server Integration Services: Business Intelligence
Monday, December 30, 2013 10:13 AM -
database Mirroring still works in SQL 2012 but it's marked for deprecation.
http://technet.microsoft.com/en-us/library/ms143729.aspx
Sofiya has already explained requirements for AlwaysOn Availability Groups. Here is the official documentationPrerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server)
http://msdn.microsoft.com/en-us/library/ff878487(v=SQL.110).aspxBalmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
--------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------------------------------------------------------------------
My Blog | Team Blog | @Twitter
Author: SQL Server 2012 AlwaysOn - Paperback, KindleMonday, December 30, 2013 10:18 AM -
Balmukund
It confuses at some degree as for STD. Edition the database mirroring may perfectly fit but it selected as deprecated.. I understand if you are on EE then AG should be using but for STD why MS force people using Log Shipping?
Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting: Large scale of database and data cleansing
Remote DBA Services: Improves MS SQL Database Performance
SQL Server Integration Services: Business Intelligence
Monday, December 30, 2013 11:32 AM -
>Edition the database mirroring may perfectly fit but it selected as deprecated.
Mirroring is merely deprecated. This just means that it will be removed in some future version of SQL Server. And it's easy to switch from Mirroring to something else, so it won't be too painful when you eventually upgrade to some future SQL Server version that doesn't support Mirroring.
For deprecated features of TSQL, the cost of using them is higher as you'll eventually have to rewrite and retest your code to upgrade.
David
David http://blogs.msdn.com/b/dbrowne/
Monday, December 30, 2013 4:29 PM