SQL databases & reporting.
We work on the PostgreSQL and SQL Server databases, queries and reports behind your numbers, so a figure can be traced back to the records it came from.
When two reports disagree
Finance and operations run what sounds like the same report and get different totals.
Finance
Counts orders by the date they were placed.
Operations
Counts the same orders by the date they shipped.
Often both are right. They answer different questions, so we write the definition down.
Tracing a figure back to its records
Every number on a report should lead somewhere you can check.
The figure
The total on the report.
Its rows
The total equals their sum.
The definition
Which records, which date, what’s left out.
The source records
Orders, refunds, accounts.
Duplicates and gaps get fixed at the source, not hidden in the chart.
The work itself
We look at a sample of real data before quoting any cleanup.Send us the report that doesn’t add up How a project runs
Where the habit comes from
We read the joins before touching the chart.
- Two years of SQL Server, C# and reporting work at Winsor
- The double-entry ledger behind UnlockAbode’s reports
- PostgreSQL and SQL Server, both
Common questions
Can you fix reports that disagree?
We can trace the definitions, source records, filters, and dates behind them. The result may be a corrected query, cleaner data, or agreement on which business event each report is supposed to measure.
Do you work with both PostgreSQL and SQL Server?
Yes. Our services cover PostgreSQL and Supabase products, SQL Server applications, and SQL-based reporting. We assess the existing schema and deployment before proposing changes.
Can you migrate or clean up our data?
We can scope mapping, validation, duplicate handling, and migration checks. Access to representative data and an agreed reconciliation method are important. Sensitive records should be shared through an approved project channel, not the public enquiry form.