All work · Commerce & services
Broken SQL replication and a leaking data warehouse fixed first, then six years replacing the Access system the floor ran on with a desktop client over a web-service layer.
A used-car buyer's reports were built on a data warehouse that was silently losing rows, and the floor ran on an unstable Microsoft Access system where two buyers could overwrite each other's work. The old system's habits had been designed into the data itself.
Fixed the replication first. Then built the production system as a desktop client over a web-service layer, following the work of the floor: quote entry with make/model filtering, appointment board, purchase and inventory detail, vehicle expenses, SMS conversations, and record locking. Rebuilt their messaging onto Twilio with push refresh.
Traced the firm's worst recurring outage to a scheduled job masking expensive SQL that was periodically driving replication out of sync, which meant the reports had been built on data that was neither live nor complete. In daily use through the last exchange.
Stack
Tell me what it does, what it is written in, and what breaks when it goes down. I will say plainly whether I can help and how I would approach it.
Tell me what it runs on