Tuesday, January 29, 2013 7:46 PM
I have an availability group running on server A to server B with synchronous commit mode. Now, I want to completely remove the AG before I upgrade from SQL 2005 to server A on cutover night.
what are correct steps to remove this availability group on primary? Do I need to remove databases from AG first before I drop the AG?
FYI...our maintenane window is not big enough to do both upgrade and re-setup AG on one night. So, I will wait for next maintenance window to setup AG again.
Tuesday, January 29, 2013 7:50 PM
AlwaysOn Avalilability Groups are a new feature of SQL Server 2012, yet you mention an upgrade from SQL 2005. So please clarify your request.
- Edited by davidbaxterbrowneMicrosoft Employee Tuesday, January 29, 2013 7:51 PM
Tuesday, January 29, 2013 8:08 PM
SQL 2005 to SQL 2012 upgrade is just normall database engine upgrade by backup and restore. After successfully upgrade to sql 2012 then I will setup availability group.
Tuesday, January 29, 2013 8:16 PM
So do you have a question?
Tuesday, January 29, 2013 8:20 PM
refer below to drop/delete AG
Tuesday, January 29, 2013 10:04 PM
High Availability groups concept is introduced in SQl2012. I am sure you knew that.
I guess you already have a SQL2012 server and have an availability group.
Now you wanted to migrate some databases from SQL2005 to SQL2012 then add these databases to those availability groups? Is this what you looking for?
If that is true, you do not have to drop the existing group. Simply migrate the databases to your SQL2012 and add to the existing group.
Well if you wanted to create a new group, you can do that.
If your answer is no. Then you need to explain more.
- Marked As Answer by Maggie LuoMicrosoft Contingent Staff, Moderator Thursday, February 07, 2013 6:53 AM