Databases Overview
Purpose: The database estate in eight reports. What instances exist, what versions they run, how much capacity they hold, what is alerting, and where the index and query problems are. Visual One reads Oracle and SQL Server through the same collection framework as the rest of the platform, which means database estate reporting arrives without deploying a separate DBA monitoring product.
What this section is, and what it is not
This is estate-level database reporting, not a query tuning tool or a replacement for a DBA’s own instrumentation. There is no query editor, no execution plan viewer, and no ability to create or rebuild an index. What it does provide is the cross-instance picture: which of your thirty or three hundred instances are on unsupported versions, near capacity, or carrying index problems, in one place and without logging into each one.
The reports in this section
| Report | What it answers |
|---|---|
| Enterprise Databases Summary | How the estate splits by platform, by count and by capacity, and how it is growing |
| Database All Instances | The full instance inventory, with edition, version, status, and capacity |
| Databases Versions | Which versions and patch levels are running, and how fragmented the estate is |
| Databases Health Alerts | What is alerting now, by condition, with acknowledgment and escalation |
| Databases Missing Indexes | Which tables the optimizer wants indexes on, and what the gain would be |
| Database Unused Indexes | Which indexes cost write performance and return nothing |
| Databases Queries Performance | Which queries take longest, and how often they run |
| Database Index Fragmentation | Which indexes and tables need maintenance |
Collection depth varies by platform
Oracle and SQL Server expose different information through their respective interfaces, so some columns populate for one platform and not the other. Edition, version, and online status are commonly present for SQL Server instances and blank for Oracle ones in the same grid, while capacity and object counts populate for both.
A blank cell in this section therefore usually means the platform does not report that field at that scope, not that the value is missing or the collection failed. The index and query reports in particular reflect what each platform’s own optimizer statistics make available.
Common actions
A quarterly estate review runs Versions for supportability, All Instances for edition and licensing, Summary for capacity pressure, and the three index reports for tuning candidates worth handing to a DBA. Health Alerts is the daily screen.
Tips
Database, schema, table, and index names are unusually revealing, because they name the business applications running on the estate. Redact them before sharing anything from the index reports, and treat instance hostnames and server addresses the same way.
Related screens
Inventory Report carries the database count alongside the rest of the estate. VM Summary covers the virtual machines these instances run on.