SQL ServerMySQLSQL Server & MySQL performance monitoring and tuning
TrueBridging reads Query Store, DMVs, the slow query log, and Performance Schema so you don't have to — and turns what it finds into a fix you can review in one click.
Blocking chain on dbo.Orders (head blocker: reporting query)
CREATE NONCLUSTERED INDEX IX_Orders_Status_Region
ON dbo.Orders (Status, Region)
INCLUDE (OrderTotal, CreatedAt);Why these engines need purpose-built monitoring
SQL Server's Query Store and dynamic management views, and MySQL's slow query log and Performance Schema, already capture almost everything you'd need to diagnose a performance problem. The gap isn't visibility — it's time. Sifting through DMV output to find which query is causing a blocking chain, or reading through a slow log to spot a pattern of parameter sniffing, is exactly the kind of work that gets deprioritized until it becomes an incident.
TrueBridging reads these same native diagnostics continuously, correlates them automatically, and surfaces the handful that actually matter — with a fix attached, not just a report.
What TrueBridging watches
Compares current query plans and durations against Query Store or slow-log history to catch regressions right after a deploy or a statistics update.
Tracks blocking chains as they form and captures deadlock graphs, identifying the conflicting statements and the indexing gap behind them.
Correlates SQL Server's missing index DMVs and MySQL's index statistics against actual query cost to rank real opportunities over noise.
Monitors tempdb contention on SQL Server and buffer pool / InnoDB hit ratios on MySQL as leading indicators of resource exhaustion.
Flags queries with highly variable execution time tied to plan reuse across different parameter values.
Tracks replication lag for MySQL replicas and Always On availability group synchronization health.
Example
A reporting query holds a shared lock while an update statement waits behind it, and three more sessions queue up behind that. TrueBridging traces the blocking chain to its head, identifies that the reporting query is missing a covering index that would let it read from a nonclustered index instead of scanning the base table, and proposes:
Once approved, the index is created online where edition support allows it, and TrueBridging confirms the blocking pattern has cleared before closing the issue.
CREATE NONCLUSTERED INDEX IX_Orders_Status_Region
ON dbo.Orders (Status, Region)
INCLUDE (OrderTotal, CreatedAt);FAQ
Yes, where Query Store is enabled TrueBridging uses it as a primary source for query-level regression detection, alongside dynamic management views (DMVs) for wait statistics and blocking chains.
Yes. TrueBridging monitors both engines through this same solution: MySQL via the slow query log and Performance Schema, and SQL Server via Query Store and DMVs.
Yes. TrueBridging surfaces blocking chains as they form, and captures deadlock graphs after the fact to identify the conflicting statements and recommend an indexing or transaction-ordering fix.
Yes. TrueBridging connects to self-managed SQL Server and MySQL as well as managed offerings including Azure SQL Database, Amazon RDS, and Amazon Aurora MySQL.