This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 63%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECK%3C/text%3E%3C/svg%3E)
I have an AG.
On secondary replica, if we remove database from AG, what will be the database status on primary replica
Additional SQL Server features and topics not covered by specific categories
Hello, Chaitanya Kiran，may I ask how you are progressing with this issue? If you're satisfied with my response, please don't forget to "Accept it." This will greatly contribute to the community and help others who may have similar problems as you do.
When removing a database from an AG, the Primary replica will have the database in a recovered state (normal looking in that it doesn't have Synchronized, or Synchronizing as a status) because it is the primary. On the Secondary it will be in Restoring mode because it is no longer in the AG.
The operation you mentioned of removing the database on the secondary replica is often used to resolve issues where the primary replica is unable to synchronize due to some reasons.
Regarding the secondary replica：
When a secondary database is removed, it is no longer joined to the availability group and all information about the removed secondary database is discarded by the availability group. The removed secondary database is placed in the RESTORING state.
The data synchronization status will become "Not Synchronized"
Refer to this.
Regarding the primary replica：
Removing a secondary replica does not directly affect the status of the primary replica's database, nor does it affect the data synchronization status.
Refer to
Best Regards,
Mikey Qiao
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
The same as before. Or more precisely, to remove the database from the AG, you need to be on the primary.
I tried this:
ALTER AVAILABILITY GROUP NormalAgge REMOVE DATABASE Northwind
This was the output:
Msg 41190, Level 16, State 8, Line 3 Availability group 'NormalAgge' failed to process remove-database command. The local availability replica is not in a state that could process the command. Verify that the availability group is online and that the local availability replica is the primary replica, then retry the command.
We can run below command on secondary replica:
ALTER DATABASE <DBNAME> SET HADR OFF
This command will disconnect all high availability connections to the target database. After executing this command, you will need to delete the removed secondary database from secondary replica;
The above actions will not affect the data synchronization of the primary replica.
If you are satisfied with the answers from me and Erland, don't forget to Accept it, as this will help others with similar issues as yours.