SQL Server and Azure SQL
review deadlock graphs, victims, processes, statements and resource ownership.
A deadlock may last milliseconds, but the failed transaction and user impact can be much longer. Mini DBA captures deadlock evidence so teams can see the competing statements, resources and transaction pattern after the event has disappeared.
Deadlock troubleshooting requires more than counting events. The useful question is why the participants acquired resources in an incompatible order and whether an index, transaction boundary or access pattern can remove the cycle. Mini DBA keeps deadlock detail beside query, plan and performance context for that investigation.
- Capture deadlock participants, statements and locked resources.
- Review deadlocks historically instead of waiting for a reproduction.
- Connect the victim and surviving transaction to query and plan evidence.
- Use alerts and AI-assisted explanation to accelerate triage.
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
correlate deadlock events with sessions, queries, locks and transaction behaviour.
MySQL and MariaDB
inspect InnoDB deadlock information alongside active workload and lock waits.
Oracle
investigate detected cycles using session, SQL, lock and wait-event context.
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
Open the captured deadlock and identify the victim, surviving participants and contested resources.
- 2
Compare the statements and transaction sequence to find inconsistent access order or excessive scope.
- 3
Inspect available execution plans and indexes before choosing a query, schema or application change.
- 4
Track new events and related alerts to verify the chosen correction under real workload.
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
SQL Server deadlocks
Read captured SQL Server deadlock evidence.
PostgreSQL deadlocks
Investigate PostgreSQL deadlock events and participants.
MySQL and MariaDB deadlocks
Review InnoDB deadlock diagnostics.
Azure SQL deadlocks
Analyse deadlocks affecting Azure SQL databases.
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.
Query performance
Prioritise expensive workload and inspect execution plans.
Analyse queries →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.