Database Design Skill

Step 2: Database selection

Map requirements to the approved database catalog (references/database-standards.md):

If the required capability is not covered by an approved database, initiate the exception process (see references/database-standards.md — Exception Process).

Step 3: Schema design (for relational stores)

• Define tables, columns, data types, and constraints
• Identify primary keys, foreign keys, and indexes
• Apply normalization appropriate to the access pattern
• Flag any denormalization decisions with justification

Step 4: Data at rest protection

For each database:

• Encryption at rest: required for all stores (document algorithm and key management)
• Access control: who/what can connect? (service accounts, no shared credentials)
• Backup and recovery: RPO and RTO targets
• See security-skill for full data protection patterns

Step 5: Multi-tenancy (if applicable)

• Is data shared across tenants, partitioned by schema, or separated by database?
• Document the tenancy model and its impact on access control and backup

Document Structure

# [Initiative Name] — Database Design

## Data Requirements Summary
[Table: Entity | Volume | Access Pattern | Sensitivity]

## Database Selection
[Approved database chosen per entity, with justification]

## Schema Design
[Tables/collections/schemas as appropriate]

## Data at Rest Protection
[Encryption, access control, backup/recovery]

## Exception Requests
[Any non-approved technology with justification and approval path]

## Open Questions

Reference Files

• references/database-standards.md — Company approved database catalog, selection criteria per use case, exception process, and data at rest requirements. TODO: Populate with your organization's approved database list and standards.