I’m reminding myself how to set up secure CrossDB access. This blog post includes a nifty diagram and follow-along example.
How can 15 be less than 13? Let’s have a look at this unexpected, but fully documented behaviour.
I’ve come up with an efficient way to monitor only specific data changes in a table.
I was investigating a mysterious Intent Shared lock in a deadlock report. Especially confusing, since the database was using an Optimistic Concurrency.
Sometimes the quickest help you can get is to help yourself. I’ve compiled a list of common problems when I’m helping out in the SQL community.
This is my go-to technique to capture errors which I can debug later.