Noted that we have to remove a database from a SQL AG before we can restore it? Why is this required? Is this because the changes are too much for a AG synch to recover from??
What other scenarios do we need to remove a database from the AG? Do we have to remove from the AG for some SQL Alter commands? Is it best practice to remove from AG then add back to AG after running a SQL Alter command?
Do we have to run alter command on the other secondary database if this alter query is run on a database outside the AG? If this is done how do we add back to the AG?,... do we use the "Join" option for synchronization. We used Automatic seeding originally when adding this database originally to the AG however since we already have a secondary database on the secondary replica w local database files on the secondary node.
We removed the database from the AG because a sql query would not run so we ran the query then we add the database back to the AG. We used the "JOIN" option. However afterwards the secondary database would not synch with the primary database? I am NOT understanding the wording used in the wizard for the JOIN option. Is it saying that you can only use JOIN when the primary database and the secondary database are identical without any differences?,... this means even a Alter broker command could break this synchronization??
What method do you recommend for adding back to the AG after the SQL alter command is run on a database outside the SQL AG?
dsk