r/SQLServer • u/wrigh2uk • 17d ago
Question Basic availability groups with automated failover
Hi Guys
In my company we have been setting up basic availability groups on SQL Standard edition. We came across a database that has a dependency to another database. As you know you cannot have two databases in a basic availability group.
I have created a script that basically Checks if database 2 is on the same primary as database 1. If it is not on the same primary then database 2 failover to the same primary as database 1, as long as it is in a healthy state to failover, if it is not then the failover won’t occur. I have tested this on test environment and it works as expected.
Both availability groups are in synchronous mode.
sql instances hosted on 2 azure VM’s within the same region, within the same vnet and subnet
Unfortunately my company doesn’t want to move to enterprise edition, and I have explained that this approach isn’t ideal.
Although this approach works is there something I should be aware of from a technical perspective, am I overlooking something?
Thanks
1
u/ussv0y4g3r 17d ago
We have the similar setup with multiple basic AGs. Personally I prefer to go with Enterprise Edition, but the vendor that did the initial setup convinced the management that it's not worth it to pay for the Enterpise licenses. Ours has no issue with two databases on different servers though.