These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Database Administration
- Data model
The tables behind Database Administration
Database Administration ships with 12 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 12
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Database and host
Database instances reference Assets and People; Assets reference Services. Backup runs reference database instances.
Response and cause
Incidents reference Services, Assets and People. Incident updates reference Incidents and People. Problems reference Services and People.
Decisions
Changes and service requests reference Services. Service requests also reference People as requester.
External evidence
Integration receipts hold provider event identity and processing outcome.
Identity
People reference Users, and Services have a People owner.
Every table, by feature
- Database Inventory4
- Backup Evidence4
- Incident Response6
- Change Control5
- Service Requests4
- Service Evidence7
- Shared and settings1
- Database instances
Database administration database instances
Linked to Assets, People - Assets
Database administration assets
Linked to Services - Services
Database administration services
Linked to People - People
Database administration people
Linked to Users
- Backup runs
Database administration backup runs
Linked to Database instances - Database instances
Database administration database instances
Linked to Assets, People - Assets
Database administration assets
Linked to Services - Services
Database administration services
Linked to People
- Incidents
Database administration incidents
Linked to Services, Assets, People - Incident updates
Database administration incident updates
Linked to Incidents, People - Problems
Database administration problems
Linked to Services, People - Services
Database administration services
Linked to People - Assets
Database administration assets
Linked to Services - People
Database administration people
Linked to Users
- Changes
Database administration changes
Linked to Services - Services
Database administration services
Linked to People - Assets
Database administration assets
Linked to Services - Database instances
Database administration database instances
Linked to Assets, People - Incidents
Database administration incidents
Linked to Services, Assets, People
- Service requests
Database administration service requests
Linked to People, Services - People
Database administration people
Linked to Users - Services
Database administration services
Linked to People - Incidents
Database administration incidents
Linked to Services, Assets, People
- Services
Database administration services
Linked to People - Assets
Database administration assets
Linked to Services - Problems
Database administration problems
Linked to Services, People - Integration receipts
Database administration integration receipts
- Incidents
Database administration incidents
Linked to Services, Assets, People - Changes
Database administration changes
Linked to Services - Service requests
Database administration service requests
Linked to People, Services
Keys and references
Human-readable numbers or names help operators identify work, while reference fields hold the actual relationships. A backup run points to a database instance, which points to a host asset; the asset points to a service. An incident points directly to a service and asset. A change points to a service, so the implementing team checks the intended database and host in the inventory before work begins. Use the provider and external event identity to reconcile a receipt with its originating event before acting on service work.
Migration order
- Load Users and People, then verify the responsible person records.
- Load Services with owners and criticality.
- Load Assets against Services, then database instances against Assets and People.
- Load backup runs against database instances.
- Load Incidents, incident updates, Problems, Changes and service requests against their referenced records.
- Load integration receipts with provider event identity and processing status.
Set up Database Administration your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.