Install Mini DBA

Mini DBA can be deployed as services, desktop tooling, or containers depending on your environment. The core production pattern is to run a Mini DBA Engine for monitoring work and a Mini DBA Console for browser access.

Mini DBA Components

• Mini DBA Engine: the background monitoring service that connects to database servers, stores configuration, validates the engine license, exposes engine service endpoints, and collects metrics.
• Mini DBA Console: the web console used by DBAs and administrators to view monitoring data, configure settings, and manage engines.

Container Deployment

Mini DBA has container images for the engine and console:

The engine stores persistent data in the engine app data folder. For Linux and container deployments this is usually /var/lib/minidba-engine; for a Windows service it is usually C:\ProgramData\MiniDBA Engine; for Azure App Service it is usually %HOME%\site\data\minidba-engine. Persist the folder used by your deployment so configuration, metrics, alerts, logs, and licensing survive container replacement or host rebuild.

The console stores persistent data for its engine connection list and web data-protection keys. Persist console storage so users do not lose configured engine connections or login cookies when the container is replaced.

Basic Deployment Steps

1. Install the Mini DBA Engine on a server that can reach the databases you want to monitor.
2. Confirm the engine service endpoint is reachable, normally on port 8734.
3. Install or start the Mini DBA Console.
4. Open the console in a browser.
5. Go to Settings and connect the console to the engine.
6. Activate the engine license from licensing, or allow trial/community behavior where applicable.
7. Go to Servers and add monitored database servers.

Choosing Where To Install Mini DBA Engine

Install Mini DBA Engine close to the databases it monitors. The engine should have stable network access to SQL Server, Azure SQL, PostgreSQL, MySQL, MariaDB, Oracle, alert delivery endpoints, and licensing services. In a simple environment, one engine can monitor all reachable database servers. In a larger estate, use more than one engine when databases are separated by customer, region, network, firewall boundary, or security ownership.

For managed service providers, a common pattern is one engine per customer site or one engine per isolated network. The Mini DBA Console can connect to multiple engines and show the combined estate in Enterprise View. This keeps monitoring traffic local to each customer environment while still giving the operations team one browser console.

Data And State To Persist

The engine data folder is operationally important. It can contain configuration, metrics, alert data, trigger data, connectivity logs, index jobs, license files, and activation bootstrap files. Treat it as durable application data rather than disposable application binaries.

Common engine data locations are:

Persist these items for reliable operation:

• Engine app data folder.
• Console engine connection configuration.
• Console data-protection keys, if the console is hosted in a container or replaced by deployment automation.
• Any external configuration files used to connect the console to engines.

Before upgrading Mini DBA, back up engine configuration and data folders. This protects monitoring settings, alert history, license state, and local configuration if the upgrade needs to be rolled back.

Security And Service Accounts

Mini DBA should not require broad administrator accounts for routine database monitoring. After the engine and console are installed, create platform-specific monitoring users using:

• SQL Server connection and permissions
• Azure SQL connection and permissions
• PostgreSQL connection and permissions
• MySQL and MariaDB connection and permissions
• Oracle connection and permissions

Use a separate operating system or cloud provider credential only when you want host-level CPU, memory, drive, or disk I/O metrics. See Host OS Login for what that access grants.

Network Requirements

The console must be able to reach each Mini DBA Engine service endpoint. Each Mini DBA Engine must be able to reach the database servers it monitors and any outbound services required for licensing, alert notifications, AI provider calls, or integrations.

Common ports:

• Mini DBA Engine service: 8734.
• Mini DBA Engine MCP HTTP API: 8735, if enabled.
• Mini DBA Console HTTP container port: 8080, normally placed behind HTTPS for production.
• Database platform ports such as SQL Server 1433, PostgreSQL 5432, MySQL/MariaDB 3306, and Oracle listener ports.

Production Recommendations

• Run the console behind HTTPS.
• Persist engine and console data folders.
• Use service accounts with least-privilege monitoring permissions.
• Configure web proxy settings if outbound internet access must pass through a proxy.
• Configure email and alert integrations before relying on production notifications.
• Back up engine configuration and data folders before upgrading.

Installation FAQ

Which component monitors the database servers?

Mini DBA Engine monitors database servers. Mini DBA Console is the browser UI that connects to one or more engines.

Can the console and engine run on different hosts?

Yes. The console must reach the engine service endpoint, normally on port 8734. The engine must reach the monitored database servers and any outbound services required for licensing or notifications.

Should the console be public on the internet?

For production, run the console behind HTTPS and use the authentication and kiosk settings appropriate for your deployment. Do not expose administrative settings or secrets to public users.

What should I check after installing?

Open Settings, connect to the engine, check Licensing, add one test database server, then review Service Log for startup or sampling errors.

Related Pages

• Getting started
• Licensing
• Settings
• Connect database servers