FIX: New Availability Group Wizard-generated scripts skip the steps for joining a secondary database to an availability group in SQL Server 2012

Article ID: 2645920 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
Expand all | Collapse all

Symptoms

Consider the following scenario:
  • You create an availability group by using the New Availability Group Wizard in Microsoft SQL Server Management Studio for Microsoft SQL Server 2012.
  • You select the Full or the Join only data synchronization preference on the Select Data Initial Synchronization page.
  • On the Summary page, you click Script in order to receive automatically generated scripts.
In this scenario, the generated scripts skip the steps that join an existing secondary database to the availability group. Therefore, if you try to use these scripts to create an availability group, the availability group cannot come online.
Back to the top | Give Feedback

Resolution

Service pack information for SQL Server 2012

To resolve this problem, obtain the latest service pack for SQL Server 2012. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2755533
(http://support.microsoft.com/kb/2755533/ )
How to obtain the latest service pack for SQL Server 2012
Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

Workaround

To work around this issue, manually add the missing steps. Specifically, add the "ALTER DATABASE DatabaseName SET HADR AVAILBILLITY GROUP" command for each availability database and secondary replica that is defined in the availability group. For example, you add the following steps:
-- On the server instance that hosts the secondary replica, 

-- join each secondary database to the availability group:

:Connect <<secondary replica 1>>

  ALTER DATABASE MyDb1 SET HADR AVAILABILITY GROUP = MyAG;

  GO

  ALTER DATABASE MyDb2 SET HADR AVAILABILITY GROUP = MyAG;

  GO

:Connect <<secondary replica 2>>

  ALTER DATABASE MyDb1 SET HADR AVAILABILITY GROUP = MyAG;

  GO

  ALTER DATABASE MyDb2 SET HADR AVAILABILITY GROUP = MyAG;

  GO
Back to the top | Give Feedback

More information

For more information about how to join a secondary database to an availability group, go to the following MSDN website:
How to join a secondary database to an availability group
(http://msdn.microsoft.com/en-us/library/ff878535.aspx)
For more information about how to use the New Availability Group Wizard, go to the following MSDN website:
How to use the New Availability Group Wizard
(http://msdn.microsoft.com/en-us/library/hh403415.aspx)
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/ )
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top | Give Feedback

Properties

Article ID: 2645920 - Last Review: November 19, 2012 - Revision: 2.0
Applies to
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Developer
Keywords: 
kbtshoot kbqfe kbfix kbsurveynew kbexpertiseadvanced kbprb KB2645920
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top