Creează un cont pentru a te abona la acest blog și a-i urmări articolele pe pagina Lectură.
Articole: 6
-
Four SQL checks for alert volume, known-fraud rate, overlap, and threshold selection before a rule reaches production.
-
Most fraud dashboards look better in a leadership deck than they work on an analyst's second monitor.
-
The standard fix doesn't work.
-
How to find connected fraud accounts using recursive CTEs and self-joins.
-
QUALIFY, frame specs, FILTER, gap-and-island, and the rest of the window-function patterns that turn five-line fraud rules into one-line filters.
-
The actual queries I run when I'm hunting fraud in transaction data.