How would you design an SQL database architecture for a centralized inventory management system tracking 200 stores (each with 500 GB of data) that supports a gradual regional rollout, minimizes costs and user disruption, and allows scaling up or down during nights and holidays?