SQL Server and Azure SQL
combine live requests, cached SQL, Query Store and graphical execution plans.
The slowest query is not always the query consuming the most total resources. Mini DBA brings duration, executions, CPU, reads, writes, waits and execution plans together so teams can prioritise the statements that matter to users and capacity.
A useful tuning decision accounts for frequency, concurrency, plan shape, data volume and the server constraint at the time. Live and historical query monitoring provides that context and makes it possible to distinguish a one-off expensive request from a small inefficiency repeated thousands of times.
- Rank slow, expensive and frequently executed statements using several workload measures.
- Inspect SQL text, waits and execution-plan operators from the same investigation.
- Compare current performance with retained query and metric history.
- Use AI-assisted plan analysis while keeping changes under DBA review.
One investigation pattern across different database platforms
Mini DBA keeps the workflow consistent while exposing the platform-specific evidence needed for a reliable diagnosis.
PostgreSQL
examine active statements, collected query statistics and EXPLAIN plan evidence.
MySQL and MariaDB
relate current workload and statement statistics to EXPLAIN output and InnoDB pressure.
Oracle
connect SQL activity, execution plans, waits and resource consumption.
Monitor every database platform from one Console
A practical investigation workflow
Start from evidence, narrow the scope and verify the result instead of applying a generic tuning checklist.
- 1
Start from a slow application period, performance alert or query ranking for the affected server.
- 2
Compare duration, executions and resource use to select the statements with meaningful impact.
- 3
Inspect waits, plan operators, warnings, estimates and relevant indexes before proposing a change.
- 4
Measure the same query and server signals after deployment to confirm the improvement and detect regressions.
Use AI beside the evidence
The Mini DBA AI Assistant can start with a focused question and optionally include the selected metrics, alerts, sessions, query, plan or event. Use it to explain evidence and propose checks; a DBA remains responsible for verification and production changes.
Ask across the estate with MCP
The Database MCP Server lets an approved AI client move from an estate-wide question to affected servers and historical detail, including multi-client workflows used by support and MSP teams.
Continue the investigation
Execution plans
Use the cross-platform execution-plan workflow.
SQL Server queries
Review active and historical SQL Server query evidence.
PostgreSQL queries
Inspect PostgreSQL statement activity and performance.
Oracle queries
Analyse Oracle SQL workload and execution detail.
Investigate the database problem, not just the platform
Use a problem-led workflow across SQL Server, PostgreSQL, MySQL, MariaDB, Oracle and Azure SQL.
Blocking and lock contention
Find the lead blocker and understand every waiting session.
Investigate blocking →Deadlock analysis
Preserve participants, statements and resources after the event.
Analyse deadlocks →Query performance
Prioritise expensive workload and inspect execution plans.
Performance history
Reconstruct incidents after the live symptoms have gone.
Explore history →
See what is slowing your databases down
Install Mini DBA on Windows, a suitable Linux VM or a supported container platform, connect an Engine and start collecting the evidence behind performance incidents.