Database Inventory

A database record identifies the engine, version, name, host asset and responsible person. The host asset belongs to a service, so an operator can move from a database name to the service affected by maintenance or an incident. Set up that link before recording backup runs. Otherwise a completed run may be technically present but hard to connect to the database people are investigating.

A database administrator starts with the database name and confirms the host asset with the service manager. The owner is a person who can answer operational questions about that instance. If a host changes, review the asset link and the service attached to that asset. Keeping an old asset would misdirect the next responder even when the engine and version still look correct.

• Service context. The service record carries its owner, criticality and current operating status.
• Host identity. The asset record carries its tag, serial number, location and status, with a link to the service.
• Database identity. The instance record carries its database name, engine, version, host asset and owner.

Agree how operators identify each host asset and who maintains asset status when a database moves. Choose the service owner who checks that the host belongs to the intended service. Give database administrators a consistent naming approach for instances and a clear owner for each one. Check the engine and version after an upgrade or migration. Decide who checks it when an upgrade or migration finishes.

For example, a team replacing a host can inspect the database record, connect it to the new asset and confirm the asset’s service. The service manager then checks whether open incidents or scheduled changes still refer to the old host. A database instance can belong to one recorded host asset at a time; the team should agree when to update that association during a move.

Take one database scheduled for work. Open its instance record and identify the owner, host asset and service. Check the asset tag against the machine the team intends to work on. Then open a backup run for that database and confirm it refers to the same instance. If the run is attached to another database, correct the linkage before relying on it for the change review.

Ask the owner to explain what would happen if the host became unavailable. The answer should lead the responder to the service and asset record, where an incident can be opened with an assigned person. This rehearsal makes the inventory useful for operations rather than a list of names.

• Database Inventory — Instances assigned to a person, with their engine, version and host asset.
• Change Schedule — Approved and active service changes alongside their planned start and end.

See database and backup evidence and service context.