Data modelling and DAX
DISTINCTCOUNT over a high cardinality transaction ID is one of the most expensive things you can ask the storage engine to do. If you understand which of your dimensions have a functional dependency on that ID, you can answer a large share of your queries with a plain COUNTROWS instead, and shrink the work for the ones that are left.
Row-level security quietly switches strategies once a table gets big enough. A recent default change moves that line from 128K rows to 512K, and the reason it is not 2 million is a nice bit of engineering.
Different models are better at different jobs. Use a premium reasoning model for planning and design. Once the plan is locked, switch to a faster, cheaper model to execute it. Stop sending the senior partner to file the paperwork.
AI-drafted content has a tell. Em-dashes everywhere, ‘I’m excited to’, ‘leverage’ as a verb. A small voice-style file teaches the assistant to sound like you instead. Half an hour once, every email cleaner forever.
