Migration is always a challenge. How many times we have stayed away from migrating product to another server or next version because we are worried what will happen once we migrate. There are two main reasons we stay away from migration 1) Everything is working fine at this moment. 2) Fear of everything will not work fine after migration.
Let us address two of this fear in brief words.
1) Everything is working fine
Even though everything is working fine there are need to upgrade to next version because new version often brings improved features as well new enhancement which can help in many ways, i.e. scalability, manageability etc. There are often cases when something is often done very complex way in current version and in next version right away out of the box the same thing is supported. I am big fan of the going to next version when it is stable.
2) Fear of application not working on next version
This is very common and we all have faced it one time or another time. We always have fear of unknown. We often worry too much because we do not know things.
The best way to solve above two problem is – Knowledge. Here is the whitepaper which talks about migration from earlier solution of the Mirroring to SQL Server 2012 solutions. This is first part of the whitepaper and second part of the whitepaper release soon.
Following is the abstract of the whitepaper.
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.
Reference: Pinal Dave (http://blog.sqlauthority.com)