SELECT TransactionID, Amount, COUNT(*) FROM Transactions GROUP BY TransactionID, Amount
I'll take 10% of savings
I'll take 10% of savings
What seemed like a very small and simple problem initially revealed itself to be massive problem that even a team of 35 struggled to maintain. The purchase history for any given item spanned multiple systems with completely different topologies of data glued together by, literally, tens of thousands of lines of SQL.
The project had been around for ~17 years when I worked on it and while data was landed in a final format where a query like the above could have been done, I wouldn't bet any serious money that the calculations were correct.
Some five or six multi-million dollar rewrites had been attempted, but could never be done.
Not to say Ohio's system is that this level, but I doubt there's a giant table sitting somewhere that such a simple query could be applied to.
I like to think that somewhere in all that SQL was an Office Space-esque line of SQL syphoning off a few cents per transaction, but was never able to find one :)
"Don't be snarky."
I'll take 9% );
8%?
Back to 10%
>Other double payments made by mistake included times that the state received multiple invoices.
I would assume each paid invoice was a new transaction ID. The real problem seems like there are two invoices being paid. Not that there are two transactions (which seems like just a symptom). It's possible that each invoice even has it's own ID.