Operations | Monitoring | ITSM | DevOps | Cloud

Grant is joined by SQL Server veteran and long-time Microsoft MVP, Hugo Kornelis, to talk all things SQL Server query tuning, execution plans, and more. You’ll hear about some of the problems Hugo’s encountered during his consultancy career, what SQL Server has in common with a highway, and Hugo’s thoughts on AI – plus much more.

Asking developers to take extra steps to pull securely is a policy that won't hold. The only approach that scales is making the private registry the default – a buffer between the developer and public registries that applies policy automatically at the global level. No extra steps, no security theater, no cognitive overhead at the point of pull. Automation and global policy configuration are what turn good intentions into a default secure posture.

See how the new Dynamic MCP Server in Resolve Actions Pro 8.1 lets AI assistants like Claude discover and execute approved Resolve runbooks through the Model Context Protocol (MCP). Watch enterprise automation happen in real time with secure, auditable execution.

Code review has always been a time sink. AI just makes the dysfunction undeniable. Luca Rossi, founder of Refactoring.fm and builder of the open source tool Tolaria, has been running one of engineering's most-read newsletters for five years, with over 170,000 subscribers. He's also been doing what a lot of engineering leaders talk about but rarely do: building a real product with AI agents to pressure-test what's actually possible today.

AI agent quality should not depend on manual checks. But for many teams shipping AI in production, agent failures are silent. The agent doesn't crash - it just gives confidently wrong answers, and your monitoring sees nothing wrong. Without automated guardrails, plausible-sounding wrong responses, hallucinations, and quality regressions reach customers before anyone notices.

AI helped your engineers ship more code. It didn't help your team ship more product. So where did the bottleneck actually go? In this Product Highlights conversation, Patrick—a principal engineer at Upsun with twelve years building back-end APIs in Go—breaks down what changed once AI agents entered the workflow. His take: "The code isn't really a problem anymore. We can write that really fast. Everything else is still a bit behind the code." We get into.