What are the Pros/Cons of sticking to a single AG per SQL Server vs setting up multiple AGs?
We have a few servers set up with AlwaysOn Availability Groups (all of them are a single primary and single secondary node) and have gone back and forth between the setup/maintenance complexity of multiple AGs each with their own listener and set of databases (as some of our pairs are configured) vs having a single AG and all the HA databases in it (as some of our other pairs are configured).
For the most part, it seems like multiple AGs are overkill and of little benefit but I want to fully understand the rationale and limitations of both approaches. I've been looking for white papers with pros/cons of both approaches and best practices but have found none.