Mini DBA helps database teams monitor multiple database platforms from one browser-based console. A typical deployment has one or more Mini DBA Engine services collecting metrics, and one Mini DBA Console showing health, performance, alerts, reports, and configuration.
Before You Begin
Make sure you have:
- Access to a running Mini DBA Console.
- The address of at least one Mini DBA Engine service.
- A console administrator login if your deployment uses restricted settings access.
- Database credentials with enough permissions to read monitoring views on each target database server.
- A license serial if you are activating a paid engine license.
First Login Checklist
- Open the Mini DBA Console URL provided by your administrator.
- Go to Settings.
- Add a Mini DBA Engine connection using the engine hostname or service endpoint.
- Test the engine connection.
- Save and connect.
- Review license status in the engine row or engine details modal.
- Activate a license if required.
- Go to Servers and add the database servers you want Mini DBA to monitor.
- Open Enterprise View to confirm the servers appear with current status.
- Configure alert recipients, recipient groups, and notification channels.
How Mini DBA Is Organized
The console navigation has global pages for estate-level work and engine-specific pages for platform monitoring.
Global pages include Enterprise View, Servers, Alerts, Reports, Settings, Service Log, and Web Log.
Engine-specific navigation appears after you connect an engine and add database servers. Each database platform has pages for activity, queries, waits, memory, health checks, alerts, and platform-specific features.
Recommended First Configuration
For a new Mini DBA environment, configure items in this order:
- Settings for Mini DBA Engine connections.
- Licensing for engine activation and license validation.
- Security settings for console access behavior.
- Email server settings so Mini DBA can send notifications.
- Alert recipients and recipient groups.
- Server groups to organize large estates.
- Servers to add monitored database instances.
First Week Checklist
After the first login, use the first week to confirm Mini DBA is collecting the right data and alerting the right people. A good first week checklist is:
- Confirm every connected engine stays online after service restarts.
- Confirm license status and licensed server counts from Licensing.
- Add one non-production database server for each database platform you plan to monitor.
- Review platform permissions using the server permissions modal.
- Add optional Host OS Login where host CPU, memory, drive, and disk I/O metrics matter.
- Configure Email Server and send a test email.
- Add alert recipients and recipient groups before enabling operational alert workflows.
- Use Enterprise View daily and confirm the status shown there matches what your team expects.
- Review Service Log for connection, license, sampling, or notification errors.
- Capture screenshots for the manual pages you plan to publish internally or on the public website.
Common First-Time Questions
Why do I connect a Mini DBA Engine before adding database servers?
The Mini DBA Console is the browser interface. The Mini DBA Engine performs monitoring work, stores engine-side configuration, validates licensing, and connects to database servers. The console needs at least one connected engine before it can add monitored database servers.
Can I monitor servers on different networks?
Yes, if each database server can be reached by one of the connected Mini DBA Engines. In distributed estates, use multiple engines and connect them to one console through Mini DBA MSP Mode.
Should I use administrator database accounts?
No for routine monitoring. Use the platform-specific connection pages to create monitoring users with the permissions Mini DBA needs. Use administrator accounts only for initial setup or testing when your security policy permits it.
Why are some pages missing data after a server connects?
Missing data usually means the monitoring login lacks a permission, an optional extension is not enabled, the host OS login is not configured, or the engine cannot reach a required service. Use the server permissions modal and Service Log to identify the missing dependency.
Next Steps
- To understand the main layout, read Console overview and navigation.
- To run more than one Mini DBA Engine, read multi-engine and MSP mode.
- To add SQL Server, Azure SQL, PostgreSQL, MySQL, MariaDB, or Oracle targets, read Connect database servers.