Yeah, but any competent DB admin will at least read the logs, do a few A/B tests, blocking out different parts or using queries which should be equivalent and then say 'something is hinky with the way this query is compiling, query z seems to give a different answer if query y is written like foo even though I see no link. Probably a subtle bug in your code I haven't spotted. Maybe ask someone who knows more about the compilation step?'
Even if they 'solve' it by rewriting query y, they'll not claim that query y was the problem, and may even leave a comment or commit log saying they didn't understand why writing it like har fixed it.
Note the word competent.. Also, insurance companies will often have opinions on what tests were valid and might reject paying for tests. So if a DB admin spins up a cluster to debug his hunch of a SQL Compiler issue, that bill will be paid by the customer and not the insurance and might bankrupt the customer..
I had an apt with a cardiologist where he literally read a standard template of care and when I tried to see if he is interested diving deeper into inflammation causes, tests and ways to avoid the standard medications which only deal with symptoms he was least interested as it all dealt with metabolic issues and not the heart per se.. the system is run to see how can a patient be billed and who owns the organ. Insurance companies have swim lanes and medical practitioners are educated and trained to remain in those swim lanes.. as long as things are kept simple for prescribed cures and billing, the gravy train continues.. it not in their best interest to solve the problem. Have you ever been to a annual physical where god forbid you discuss issues that are not part of the normal annual health checkup? You will actually be asked to schedule a separate appointment as the billing for that is separate..
A lot of "functional medicine" happens outside of insurance payment coverage.
Some more interesting things to follow:
https://cholesterolcode.com/https://cynthialimd.com/faqs/
Even if they 'solve' it by rewriting query y, they'll not claim that query y was the problem, and may even leave a comment or commit log saying they didn't understand why writing it like har fixed it.