Did you do your part? RT if you voted! #BroncosCountry

The Grim Leaper, Brazilionaire, The Redeemer, Mile High Hog, The Trevolution, Pogo De Chao, Mount Treverest, The Amazon Painforest, T-Bone, Rebound de Janeiro, Samba Mamba, The Condor, TB7, Copacaslamma, The Elevator, Brazilian Bench Lift, The Big Carnival, Trevon-Eleven, The Slamazon, Trayzorback, Air Brazile, Windmill Brazile, Blocka Nova

Another update to my leukemia diary. Bad news this time. sqlserverfast.com/blog/hugo/…

Cason Wallace grabbed Jokic’s leg on the screen to make him trip him. We’ve never seen this level of foul grifting 😂😂

WE ENDED THE 20 POINT STREAK

ENDED SGA’s RANDOM SCORING STREAK LETS GOOOOOO

SGA is such a crybaby ass bitch

OKC's flopping is OUT OF CONTROL 😂

DAD HE HIT ME!!! DADDDDDDD

Starters assemble #DigDeep | @SouthwestAir

🎥 How SQL Server People Can Stay Relevant With AI youtube.com/watch?v=s3YNY4vX… 🎥

The wait is over. The 2026 NBA season starts TONIGHT.

You can’t tune what you haven’t measured! Register now at sprou.tt/1xuzlX8FuG2 #SQLServer #Oracle #Postgresql #MariaDB #MySQL #SAPHANA #DatabasePerformance sprou.tt/1xuzlX8FuG2

Wait types are the most misread numbers in SQL Server. So I caused six of them on purpose, one at a time. I took a profile of each while it was happening. The lab is one table of 2.5 million rows, about 1.15 gigabytes, on SQL Server 2025. Every figure below is the wait recorded for my own session while the workload ran, not a server total. Where a wait behaved differently from its reputation, I have said so rather than tidied it away. Each section carries a profile card with the reading of that wait. The measurements stay in the text, where they can keep the conditions they were taken under. One number to hold in your head before we start. A lock wait in this lab cost 81,927 milliseconds across a single wait. A processor wait in the same lab cost 3 milliseconds across 398 waits. Sorted by count and sorted by time, a wait list gives you two different answers. Only one of them is about your problem. Read more here: blog.sqlauthority.com/2026/1…

A customer asked a six-person team why their large invoices were billed slightly differently. The answer was a four-line rounding rule. The person who wrote it had left eight months earlier. The team asked their AI assistant. It explained the code perfectly and even offered a cleaner version. What it could not tell them was why the rule existed. It might have been a regulatory requirement, or a promise to a big customer. It might have been a workaround for a system shut down in 2021, or just a mistake nobody had noticed. They left the code alone and told the customer the invoice was correct. That was true. Nobody in the company could say why it was true. This is tribal knowledge, and AI makes losing it easier to miss. New engineers used to text the person who left. Now they ask the assistant, get a good answer about what the code does, and feel caught up. The old failure was loud. The new one feels like competence. Two things that actually help: 1. 𝗔 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗹𝗼𝗴 𝗶𝗻 𝘁𝗵𝗲 𝗿𝗲𝗽𝗼, 𝗻𝗲𝘅𝘁 𝘁𝗼 𝘁𝗵𝗲 𝗰𝗼𝗱𝗲. Four lines per decision: the choice, the alternative, the reason, and what would make this wrong. The last line matters most, because it tells the next person when they can safely undo it. 2. 𝗢𝗻𝗲 𝗿𝗲𝗰𝗼𝗿𝗱𝗲𝗱 𝗵𝗼𝘂𝗿 𝗯𝗲𝗳𝗼𝗿𝗲 𝘀𝗼𝗺𝗲𝗼𝗻𝗲 𝗹𝗲𝗮𝘃𝗲𝘀. Skip the exit doc. Ask them: what breaks if a new person makes the obvious change? What looks wrong but is right? What failed before? Which customer deals live in no document? The code is not the knowledge. It is the leftovers of a decision nobody wrote down. Start the log this week. Then go ask your longest-serving person why things work the way they do. Full post: blog.sqlauthority.com/2026/1… #SQLServer #DataEngineering #AI #EngineeringLeadership

Sheeeeeesh 🥶

Join me on Oct 22 to learn more about #Database performance baselining and benchmarking. Hope to see you there! sprou.tt/1jYarkWdThT

Alright man Jokic just out here doing bullsh*t and it’s WORKING lmaoo LOOK AT THIS PASS 😭

#DBAs know that keeping a #database running efficiently comes from understanding the first principals of how they use CPUs, memory, and other resources. Join this session to learn the details. Hope to see you there! sprou.tt/1brp8vKKeOj

Nikola Jokic lists his NBA Mount Rushmore 🐐 🔶 Bill Russell 🔶Michael Jordan 🔶Wilt Chamberlain 🔶 Stephen Curry "I'd probably say Bill Russell, for his championship titles. Michael Jordan, because he changed basketball. Probably Wilt Chamberlain, for all his numbers and completely insane stats. And I'm going to put Steph Curry, because he changed basketball and he's more or less from my generation. I've played against him and he really changed the game, in his own way. Those are my four players." (via Sport Bible)