Connect A Database Server To Mini DBA

Start Here

Manual Home Installation Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Legacy Documentation

Connect database servers to Mini DBA so the engine can collect health, activity, performance, query, wait, alert, and platform-specific monitoring data.

Supported Database Platforms

Mini DBA Console routes include monitoring pages for:

Connection Workflow

Open Settings and confirm the correct Mini DBA Engine is connected.
Open Servers.
Add a new server for the target platform.
Enter the server name, endpoint, display name, and authentication details.
Test the connection if the form provides a test option.
Save the server.
Wait for the engine to collect its first samples.
Open the platform overview page from the navigation tree.

Choose The Right Engine First

In a single-engine installation, every monitored server belongs to the same engine. In a multi-engine installation, confirm which engine should own the new monitored server before you add it. Choose the engine that has network access to the database host, the correct license capacity, and the right operational ownership.

If the console is in MSP mode, a database server in one customer network should usually be added to that customer's engine, not to a central engine that cannot reach the database. Clear engine ownership makes alerts, logs, history, and licensing easier to understand later.

Permissions

Use credentials that can read the database metadata and performance views required for monitoring. The exact permission set depends on the platform and which pages you want to use. For example, query, wait, health check, lock, file, and permission pages may require different system views or catalog access.

Use the platform-specific guides for connection fields, least-privilege SQL examples, and optional host OS login:

Database Login Vs Host OS Login

The Add Server panel collects database connection details. That login is used for database-level monitoring such as sessions, queries, waits, metadata, health checks, alerts, and permissions.

Host OS login is separate. It is configured after a server has been added, from the server permissions or connectivity modal. Host OS login is optional and is used for operating system metrics such as CPU, memory, drive capacity, and disk I/O. PostgreSQL, MySQL, MariaDB, and Oracle use the shared Host OS Login panel. SQL Server uses SQL Server DMVs for some host information and Windows performance/WMI access for additional counters.

Data Freshness After Adding A Server

After a server is added, the engine needs at least one collection cycle before every page has data. Some pages update quickly, such as activity and current status. Other pages depend on less frequent sampling, optional extensions, Query Store, log availability, or host OS credentials. If a page is empty immediately after adding a server, wait for the next sample and check Service Log before changing configuration.

Connection Troubleshooting

Confirm the Mini DBA Engine can reach the database host and port.
Confirm firewalls allow traffic from the engine server.
Confirm the database login can connect from the engine host.
Confirm the target server has not exceeded the engine license connection limit.
Right-click the server in the navigation tree and open Connectivity Log for per-server connection and data-access errors.
Check Service Log for connection and sampling errors.
Check Web Log if the console form or UI behavior fails.

For a step-by-step workflow, see Troubleshoot Database Connectivity.

Connection FAQ

Why does the Add Server panel ask for different fields by platform?

Each database engine has different connection requirements. Oracle needs a service name and listener port. Azure SQL needs an authentication mode. SQL Server can use Windows authentication or SQL authentication. PostgreSQL and MySQL/MariaDB use host, username, and password in the current Add Server form.

Where do I add SSH credentials?

Add the database server first. Then open the server permissions modal and configure OS Login. SSH credentials are not entered in the Add Server panel.

What happens if permissions are incomplete?

Mini DBA may still connect, but some pages will be empty or partial. Use the permissions modal and the platform-specific connection guide to grant the missing permission.