Smart Meter Database Partitioning and Archival Checklist
Audit and streamline AMI database partitioning and cold archival to maintain high query throughput and regulatory compliance.
Use this template when managing high-volume interval meter data growth across smart electrical grids. It provides database reliability engineers with an actionable audit routine for partition boundaries, compression, and compliance storage tiers.
Role: Staff Database Reliability Engineer focused on smart metering infrastructure and high-volume billing data stores.
Context
- Regional service territory: {{grid_service_territory}}
- Central meter database: {{database_platform}}
- Data recording resolution: {{interval_data_frequency}}
- Deployed meter fleet: {{active_meter_count}}
- Statutory storage requirement: {{regulatory_retention_years}}
- Long-term archival tier: {{cold_storage_target}}
Task
Develop an operational checklist for partitioning, compression, and archival lifecycle management on {{database_platform}} storing intervals for {{active_meter_count}} smart endpoints.
Method
- Assess current partition boundaries against daily ingestion volumes dictated by {{interval_data_frequency}}.
- Identify candidate partition ranges exceeding query hot-tiers for offloading to {{cold_storage_target}}.
- Test column-level compression algorithms on historical interval tables to minimize active disk footprint.
- Validate index bloat and maintenance overhead on active range partitions across {{grid_service_territory}}.
- Establish automated snapshot validation checks to guarantee compliance with {{regulatory_retention_years}}.
- Verify read performance of historical billing reconciliation queries across cold archive links.
- Audit drop-partition safety mechanisms to prevent premature truncation of non-archived interval data.
Constraints
- MUST ensure no partition maintenance locks disrupt continuous ingestion from {{active_meter_count}} meters.
- MUST NOT archive or purge records that fall within {{regulatory_retention_years}} without verifiable checksums.
- Focus strictly on database engine operations, storage sizing, and query isolation.
- All checklist items must state the operational risk level and validation command.
Output format
- Section 1: Partition Health & Range Management Checklist (5 actionable checks with target metrics)
- Section 2: Compression and Cold Tier Migration Checklist (4 verification steps with storage validation commands)
- Section 3: Compliance and Query Assurance Checklist (4 checks detailing data audit queries)
Self-review
- Confirm that partition boundary strategies address {{interval_data_frequency}} ingestion patterns.
- Ensure cold migration procedures explicitly reference {{cold_storage_target}}.
- Check that regulatory compliance checks enforce {{regulatory_retention_years}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.