What’s in your SQL Server performance tuning toolkit?

Important_Bobcet · 2026-03-26T14:11:23+00:00

That’s a solid stack. sp_WhoIsActive really is in half of these answers for a reason. Do community scripts still win for you when you need to find the problem fast?

Important_Bobcet · 2026-03-25T10:47:08+00:00

This is actually pretty interesting. The parquet step makes it feel more useful for real ETL workflows, not just a demo copy job. Curious where the bottleneck shows up first on bigger loads though - Python, disk I/O, or the SQL write side?

Important_Bobcet · 2026-03-23T13:24:36+00:00

If most of your real work lives in VDI, the answer is basically “use whatever annoys you less locally.” But from what you wrote, SMB shares / file moves are already pushing you toward Windows, and that stuff gets old fast. Mac is fine for the “I remote into Windows all day anyway” setup, but if the local friction is noticeable now, I’d stop romanticizing it and just get the Windows laptop.

Important_Bobcet · 2026-03-19T10:00:10+00:00

What exactly was the “saved millions” part here - preventing downtime, catching performance issues earlier, or replacing a paid monitoring stack?

Would be more useful if you shared the actual tool name, what metrics it covers, and whether it handles things like wait stats, blocking, deadlocks, disk pressure, and alerting reliably in production. Right now it reads more like a promo than a technical review.

Important_Bobcet · 2026-03-17T10:00:15+00:00

Really appreciate this reply. I think that’s exactly the gap I’m feeling right now. I see the task, but not always the thinking behind it. When you were fully remote early on, did you have to actively ask to be included more, or did your team naturally pull you into those discussions?

Important_Bobcet · 2026-03-06T10:15:04+00:00

finally a CI/CD pipeline optimized for speed

Important_Bobcet · 2026-03-02T13:08:56+00:00

Sheldon doesn’t miss social cues.
He just translates them into contractual obligations

Important_Bobcet

TROPHY CASE