Azure Database Space Optimization¶
This learning hub organizes the repository's demos and guides for understanding allocated, used, and reclaimable capacity across Azure database services. The objective is not simply to make a database smaller; it is to choose the right data-lifecycle, storage, index, partition, or cache policy for the workload.
Warning
These guides are learning material. Reclaim operations can be long-running, create blocking or resource pressure, change fragmentation, affect replication or backup behavior, and interact with service-specific limits. Test with representative data, take a recovery-ready approach, and follow the current official guidance for the exact service and tier.
flowchart TB
A[Assess allocation, use, and growth] --> B[Choose a targeted service-specific strategy]
B --> C[Validate performance, durability, and cost]
Assess space and riskStart with measurement, workload context, recovery readiness, and a controlled change plan.
Relational database strategiesExplore Azure SQL, SQL Managed Instance, SQL Server on VMs, PostgreSQL, and MySQL patterns.
Non-relational data strategiesReview Cosmos DB, Cassandra, and cache retention and memory-management considerations.
Start here¶
| Need | Start with |
|---|---|
| Determine whether a space issue needs action | Assess space and risk |
| Plan a relational database change | Relational database strategies |
| Manage retention or memory in non-relational services | Non-relational data strategies |