As you might be aware of NDB supports Microsoft SQL Server (MSSQL) Windows Server Failover Cluster (WSFC) based databases including both Failover Cluster Instance (FCI) and always on availability group (AAG) as well as standalone databases.
See information about NDB supported configurations for MSSQL here
So now on to the actual quick tip 🙂
If you have a WSFC with AAG based DB(s) plus standalone DB(s) and would like to managed both type with NDB you need follow the below registration process:
- WSFC based DB(s)
- Standalone DB(s)
By doing this you’ll register all DB Server VMs in the WSFC in step one. If you start with the standalone DB you’ll only register one DB Server VM with NDB.
Other blog posts in the Quick Tip series are:
- NDB Quick Tip IV – NDB Pulse Telemetry
- NDB Quick Tip III – Supported Functionalities per DB Engine & DB Server VM Operating System
- NDB Quick Tip II – PostgreSQL extensions
- NDB Quick Tip I – API v0.9
- NDB Quick Tip V – New NDB Documentation Structure
- NDB Quick Tip VI – DB Server VMs with same IP Address
———————————————————————————
