Mini DBA Product Documentation


Start Here

Console

SQL Server

Azure SQL

PostgreSQL

MySQL/MariaDB

Oracle

Settings And Integrations

Legacy Documentation

Mini DBA is a database monitoring and management platform for SQL Server, Azure SQL, PostgreSQL, MySQL, MariaDB, and Oracle. The Mini DBA Console gives DBAs, managed service providers, and technical teams one place to review server health, alerts, performance data, licensing, and engine configuration.

Mini DBA console enterprise view

Use this manual to install Mini DBA, connect one or more Mini DBA Engine instances, license an engine, add monitored database servers, and use each console page for day-to-day database support.

Start Here

Main Console Areas

Database Monitoring Guides

Settings And Integrations

Typical Workflows

  1. Install and start at least one Mini DBA Engine.
  2. Open the Mini DBA Console and connect to the engine from Settings.
  3. Activate or verify the engine license using licensing.
  4. Create a least-privilege monitoring login using the platform-specific connection guide.
  5. Add database servers from the Servers page.
  6. Organize servers with Server Groups where groups help navigation, reporting, MSP work, or access control.
  7. Add optional host OS login where CPU, memory, drive, and disk I/O metrics are required.
  8. Review health and activity in the engine-specific monitoring pages.
  9. Use Connectivity Log and Troubleshoot Database Connectivity when a server connects but does not collect data.
  10. Configure alerts, email, and notification channels.
  11. Reuse alert policies with Copy, Export, And Import Alert Configuration when several servers or engine instances should share the same thresholds and routing.
  12. Use Execution Plan Analysis and AI Assistant for guided performance tuning, alert triage, plan review, and BYO AI workflows.

Who This Manual Is For

This Mini DBA manual is written for database administrators, platform engineers, managed service providers, and application support teams who need practical database monitoring documentation. The pages are organized around real console workflows rather than internal product architecture. If you need to install Mini DBA, connect SQL Server, monitor Azure SQL, review PostgreSQL permissions, troubleshoot MySQL performance, or understand Oracle health checks, start with the workflow page closest to your task.

Mini DBA is useful when a team wants database monitoring without relying on one database platform only. A single console can show SQL Server, Azure SQL, PostgreSQL, MySQL, MariaDB, and Oracle data. This matters for mixed estates, MSP environments, acquisitions, development teams with more than one database engine, and support teams that need a consistent way to answer "what is slow", "what is blocked", "what changed", and "who needs to be alerted".

Search-Friendly Topics Covered

The manual includes dedicated pages for common database monitoring searches:

  • SQL Server monitoring, Query Store, waits, deadlocks, Agent jobs, Always On, health checks, and performance tuning.
  • Azure SQL monitoring, elastic pools, database waits, locks, Query Store, permissions, and performance tuning.
  • PostgreSQL monitoring, permissions, logs, wait analysis, memory, I/O, indexes, deadlocks, and host OS metrics.
  • MySQL and MariaDB monitoring, InnoDB, permissions, deadlocks, I/O, memory, and performance tuning.
  • Oracle monitoring, activity, waits, queries, memory, health checks, permissions, and host metrics.
  • Execution plan analysis for SQL Server, Azure SQL, PostgreSQL, MySQL, MariaDB, and Oracle.
  • AI-assisted database performance tuning, BYO AI setup, alert triage, execution plan interpretation, and token/privacy guidance.
  • Copying alert configuration between servers and importing or exporting alert trigger configuration between Mini DBA Engine instances.
  • Connectivity log review, database connection troubleshooting, Windows WMI monitoring, and server groups for navigation, reporting, MSP operation, and access control.

Each connection guide includes a least-privilege monitoring user example where the product has permission checks for that platform. Those examples are intended to help administrators create accounts that collect monitoring data without using broad administrator accounts for day-to-day Mini DBA monitoring.

For managed service providers and distributed database teams, Mini DBA MSP Mode explains how one console can connect to multiple engines, how engine selection affects navigation, and how to view alerts across all engines or only the current selected engine.

For execution plan workflows, Mini DBA Execution Plan Analysis links to the database-specific plan viewers and explains how to drill into expensive operators. For AI-assisted workflows, Mini DBA AI Assistant explains how page context, optional metrics, sessions, alerts, execution plans, BYO AI, and free token limits work.

Manual FAQ

Is Mini DBA only for SQL Server?

No. Mini DBA includes SQL Server monitoring, but the console also has monitoring pages for Azure SQL, PostgreSQL, MySQL, MariaDB, and Oracle.

Do I need one Mini DBA Engine per database server?

No. A Mini DBA Engine can monitor multiple database servers, subject to network reachability and the engine license. Larger or segmented environments can use multiple engines connected to one console.

Where should new users start?

Start with Installation, then Getting Started, then the platform-specific connection page for the database engine you want to monitor.

Are screenshots included?

Every public page has a meaningful screenshot placeholder. Add the final PNG files under Documentation/Manual/screenshots before publishing the generated HTML.

Related Documentation

For container deployment details, see the technical Docker installation document at Documentation/installation.md in the source repository.