Requester: Harbor Freight platform lead. Done: distinct local OLTP and analytical intent, with a reconciled recommendation for booking correctness, connection, freshness and historical recovery.
Harbor Freight is reviewing its booking and reporting data paths. You will store a transactional database configuration and a separate analytical configuration, then check how uniqueness, uncertain outcomes, reporting freshness and restoration affect the business promise. Each accepted decision stays in the carried local account.
The browser does not run either database or move any records between them. A second database is not a tested recovery path or a live report. Finish with an evidence-based recommendation that identifies the authoritative transaction, permitted connection and required restored data. The final statement must distinguish what the model configured from what a production rehearsal would have to demonstrate.