Trying to understand SQL 2016 Basic Availiability Groups (BAGs), coming from SQL 2008 R2 environment with no clustering, no mirroring, just regular backups. I am not a DBA and we are a small company. Been reading TechNet, various SQL blogs. I understand the 2-node no-read, no-backup situation, but it's one step better than we have now and affordable. Looking to architect and budget for 2017 upgrades/migrations (SharePoint 2016 and some non-Microsoft platforms). I have some really basic questions:
Each primary database would be in a BAG with its secondary. So if we have 20 databases, we would have 20 BAGs, yes?
Can we have one SQL server that would host the secondary databases for two different primary database servers? (ergo, three server cluster) Example: SharePoint databases on SQL1, non-SharePoint databases on SQL2, and the secondary databases of both on SQL3. With Windows clustering only, not also SQL clustering.
Thanks,
Joan