A reporting copy of the ERP, without touching production
Selected ERP tables are copied on a schedule into a cloud SQL warehouse for reporting, while the live ERP remains the financial system of record.
Built in my employed role ยท Demonstration data
The issue
Operational reporting needed current ERP data without placing report queries against the live production system or rebuilding the same extracts for every reporting tool.
Why it mattered
The live ERP must stay responsive and authoritative. A separate reporting copy gives analysts and dashboards a shared place to query without competing with operational transactions.
What I built
A scheduled raw-data replica using a sync tool, selected ERP tables, a cloud SQL warehouse, defined sync channels and documented connections for SQL reports and business intelligence tools.
How it works
The first run copies each selected table in full. Later runs transfer changes incrementally into the reporting copy, where reporting tools can query it without touching production.
Outcome
The result is a shared read-only ERP reporting foundation. It currently mirrors ERP tables only, not CRM or operational files, and it does not claim an automated transformation or self-healing layer.
