I am running scripts to partition two tables. The database is a part of a high availability group. Normally I would remove the database from the high availability group, change the recovery mode to simple, and run the scripts. However, the
individual that I report to wants me to run the scripts with the database still in the high availability group. I think because they don't want to take the databasse down in production.
I am currently running a test in development and the scripts ran find but I discovered that the database is Not Synchronizing/Suspect on the secondary server.
I tried to resume data movement but it fails. I get an error message "A timeout occurred while waiting for the operation to complete. Object Explorer could not be updated. Try refreshing Object Explorer manually.". I right clicked on the database and clicked on refresh. I also tried to run the following: ALTER DATABASE [ldm_carepoints] SET HADR RESUME; I also restarted the services.
Is there anything that I can do to fix this without removing the database from the high availability group and readding it? Or is that the only solution?
Also, is it better to run the scripts when the database is not a part of the high availability group and is in simple mode or is it ok to run the scripts when the database is a part of the high availability group and is in full mode. I want to give the individual a good reason why it is best to take the database off of the availability group and place the database in simple mode.
lcerni