Clustering

External Article

Migration Guide: Migrating to SQL Server 2012 Failover Clustering and Availability Groups from Prior Clustering and Mirroring Deployments

  • Article

This paper provides guidance for customers who prior to SQL Server 2012 have deployed SQL Failover Clustering for local high availability and database mirroring for disaster recovery, and who want to migrate to SQL Server AlwaysOn. It describes the corresponding SQL Server AlwaysOn scenario and the migration paths to SQL Server AlwaysOn. It also contains the important knowledge and considerations that you must know in order to successfully migrate to a HADR solution based on SQL Server AlwaysOn technology, which implements AlwaysOn Failover Cluster Instances for high availability and AlwaysOn Availability Groups for disaster recovery.

2012-04-13

2,738 reads

Blogs

SQL Server 2025 Generally Available

By

This was announced last week at Microsoft Ignite and it's been covered by others...

Chatting with Power BI: Who Benefits from This Conversation?

By

"Dave: Open the pod bay doors, HAL.HAL: I’m sorry, Dave. I’m afraid I can’t...

A Quick Look at Redgate Data Modeler

By

Redgate acquired a data modeling tool from Vertabelo recently and I wanted to explore...

Read the latest Blogs

Forums

Steps for Installing AlwaysOn Availability Groups - SQL 2019

By Ginger Daniel

Comments posted to this topic are about the item Steps for Installing AlwaysOn Availability...

SQL Server 2022 order by bug?

By hugo-939487

Hi, I was using order by on a column with characters and saw something...

SQL Server 2025 Build List

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server 2025 Build List

Visit the forum

Question of the Day

Getting The Database Name

I run this code to connect to SQL Server 2022 from the command line.

sqlcmd -S localhost -E
At the command line, I run these two commands:
SELECT ORIGINAL_DB_NAME()
GO
What is returned?

See possible answers