Databases

This inventory belongs to the DBA team, and Regulaxy reads it live. The column set comes from the source itself, so it looks different in every deployment, and different between Oracle and MSSQL in the same deployment.

Sources

The source selector sits in the toolbar and changes shape with what exists:

Sources configured	What is shown
One	A label only, naming the source
Two	An Oracle / MSSQL switch
Three or more	A dropdown, each entry naming the object it reads — at that point the label alone stops telling them apart

Each source keeps its own column order. In a deployment with no source configured, the screen says so rather than rendering an empty table.

The columns

This is the one table in the product that scrolls sideways. Everywhere else the columns are fitted to the width of the screen; here there are twenty or more, they arrive at runtime, and there is no administrator-set priority order to fit them against — so fitting them would leave all of them below a legible width. The identity column stays frozen while you scroll.

Three fields that are written back

Field	What it is for
System	The business system the database belongs to
System owner	Who is responsible for it. Filled in automatically when the system is chosen
Coordination note	A free-text note from the team

System is picked from a list — the same list of systems the business-impact register works against, and that is what wires the two together.

The write goes to the source's write object, which is not necessarily the object it is read from. Both objects are named in the information line under the table, because when an update is rejected that is the first question. A rejected update states the reason and returns the cell to its previous value.

The database record

Clicking a row opens a record. The key is the database name together with its host — PROD on two hosts is two databases, and a shared overlay between them is a data-integrity bug wearing a UI bug's clothes.

A row whose source has no database-name column does not open a record, and the screen says so rather than leaving a click that does nothing.

On the record you can add custom fields of your own. They are stored in Regulaxy, alongside the inventory, and are not written to the source.

Actions and states

• Multi-row selection feeds the scheduling wizard, up to 50 records; anything beyond that is stated before it proceeds.
• CSV and Excel export what is on screen.
• When the source is unreachable the screen shows demo data and says so in a banner that cannot be dismissed. Presenting fictional rows as the inventory is worse than an error message.

Who may do what

Permission	What it allows
View databases	Reading the inventory and the record
Edit coordination fields	Writing the three fields above back to the source
Export databases	CSV and Excel