- Task
- Version · 6.0.2
- Measure
Measure drift across your databases
Last updated: November 17, 2026
The Drift Detection dashboard reports how widespread schema drift is and whether it is spreading.
Before you begin
Contact us to enable Change Intelligence.
At least one
diffordiff-changelogrun has been reported to the server. Those are the operations these figures are computed from.
Procedure
Open the Drift Detection dashboard
Under Monitor, open Drift Detection. The window follows the time range you select and defaults to 30 days. The same five figures appear on the Operations Dashboard, always over the last 30 days.
Note which figures count operations and which count objects
Drift Detected and Total Drift Items do not divide into each other. Drift Detected counts operations, so a database checked ten times while drifted contributes ten. Total Drift Items counts objects and deduplicates per database, so the same missing index found by ten consecutive checks contributes one. Avg Drift Items is the figure that relates them, and it answers how much drift a typical affected database is carrying.
Check which direction each should be moving
Drift Rate and Database Coverage read in opposite directions: a falling drift rate is good, and rising coverage is good.
Read them together. A drift rate that falls because you stopped checking is not an improvement, and coverage is what shows that. Database Coverage divides by every registered connection that is not archived, so archive the connections you no longer use rather than leaving them to hold the figure down.
If the metrics cannot be loaded, the tiles are replaced with an Unable to load drift metrics message rather than showing zeros, so an unavailable metric is never mistaken for a real value of zero.