New answers tagged

10

It is not possible to delete a database that currently resides in an availability group. It is also not possible to restore over top of it while it remains in the availability group. Thus, this database was not in an availability group to begin with. What you are describing is not possible as you will get an error if the database is involved in Always On. ...


0

I think the question has a wrong assumption. So is there a way to keep a single (primary) replica server active in the AG for the databases without removing them but keeping the log file from growing or being stuck in 'AVAILABILITY_REPLICA'? ... I'd rather not remove the AG as the listener is actively used and would require reconfiguration of ...


4

Since you have configured AlwaysON as Asynchronous, it will be in synchronizing state. Should it say Synchronized at some point? If you want to do a planned failover, you should alter your availablity group to synchronous and then do a failover. When you change the synchronization method to synchronous and when the secondary has catch-up with primary, ...


1

As I understand your question, the answer is Yes. 1 SQL instance can act as a secondary for multiple Availability Groups. Listeners will point to the appropriate AG. You may have some security concerns to address if the user base of the different AGs is a different set of users...make sure they can't access each other's databases in the case that they are ...


0

Yep, you don't need HAProxy with the newest versions pgpool-II. I'm not sure in which version it is introduced, but "watchdog" feature that is now embedded in pgpool does everything needed for automatic fialover and real HA. Take a look at this post - it'll help for sure.



Top 50 recent answers are included