Connect Mini DBA Console to multiple Mini DBA Engines and monitor servers, alerts, metrics and history from one Multi-Engine view. See Multi-Engine Mode.
When to use multiple engines
Use multiple Mini DBA Engines when:
- You monitor separate customer environments.
- You have different sites, regions, or networks.
- Database servers cannot all be reached from one monitoring host.
- You want independent engine services for resilience or ownership boundaries.
- You run a managed service provider workflow from a central console.
Multi-Engine settings and multi-Engine mode
Use this page when you need to add, connect, test, edit, or remove engine connections. Use Mini DBA Multi-Engine Mode for broader operational guidance covering customer separation, alert scope, server groups, licensing, and daily cross-engine triage.
The important idea is ownership: each monitored database server belongs to one engine, and that engine owns the sampling, alerts, service log entries, and license usage for that server.
Add multiple engines
- Open Settings.
- Select Connect Mini DBA Engine.
- Add the first engine and save it.
- Repeat the process for each additional engine.
- Enable Auto-connect on startup for engines that should connect automatically.
- Use the action menu to test and connect each engine.
- Open Enterprise View to review the combined estate.
Engine roles and permissions
Each engine connection can have its own credentials and role. Read-only engine access may allow monitoring review while administrator access is required for settings changes, server changes, and license actions.
Community Edition permits one configured Community engine per Console. Additional Community engines remain visible in the connection table as disabled, with an explanation and a Recheck licence action, but the Console does not subscribe to them or show their monitoring and alert data. Licensed engines do not count toward this limit. The configured order determines which Community engine receives the allowance; disconnecting it or disabling Auto Connect does not move the allowance to another entry.
License behavior with multiple engines
Each Mini DBA Engine has its own license. Activating or deactivating a license affects only the selected connected engine instance. Review each row in Settings to confirm license name, SQL connection usage, and expiry per engine.
Operational tips
- Use descriptive engine names such as customer, site, region, or environment.
- Keep engine service endpoints consistent and documented.
- Review disconnected engine detail rows for last successful connection, disconnected since, next retry, and error messages.
- Use Server groups to make large multi-engine estates easier to navigate.
- Use Mini DBA Multi-Engine Mode for all-engine alert triage and selected-engine investigation workflows.
Multi-Engine FAQ
Does one Console license all engines?
No. Each connected Mini DBA Engine has its own license state, monitored server count, and expiry information.
What happens if one Engine disconnects?
Other connected engines can continue to show data. The disconnected engine row should show connection status and retry information.
When should I use more than one Engine?
Use multiple engines when network boundaries, customers, regions, ownership, resilience, or scale make one monitoring host impractical.
Where do I deactivate an Engine license?
Use the connected engine row on Settings or the licensing workflow in Licensing.