Assume that you use Microsoft SQL Server 2014 or 2016 AlwaysOn Availability Groups and have permission to change ownership of an availability group. After the owner of the availability group is dropped from SQL Server, you can't change the ownership of the availability group. For example, when you try to change ownership of the availability group by executing the ALTER AUTHORIZATION ON AVAILABILITY GROUP statement, the execution fails, and a dump file is generated.


This problem was first fixed in the following cumulative updates for SQL Server:

    Cumulative Update 5 for SQL Server 2016 RTM

    Cumulative Update 2 for SQL Server 2016 SP1

    Cumulative Update 4 for SQL Server 2014 SP2

    Cumulative Update 10 for SQL Server 2014 Service Pack 1

Note After you install this update, you can take ownership of an availability group even after the owner is dropped. 

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2016

Latest cumulative update for SQL Server 2014


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!