Sherpa of Data

Author: Kevin

  • Stop Guessing: Build a “Who Has Access to What” Dashboard

    —

    by

    Kevin
    in

    By now, a few things should be clear: Your access model isn’t a hierarchy – it’s a graph.That graph contains hidden exposure paths.And those paths can be measured using real signals. That’s a solid foundation. But there’s still a gap: You can’t manage what you can’t see. SQL queries are great for analysis.They’re terrible for…

  • You Can’t Fix What You Can’t Measure: Introducing the Access Risk Score

    —

    by

    Kevin
    in

    By this point, two things should be very clear: Your access model is not a clean hierarchy.It behaves like a graph of inherited, interconnected permissions. Which leads to a practical problem: If access is a graph… how do you measure risk inside of it? Because listing roles doesn’t work.Auditing permissions doesn’t scale.And “review everything quarterly”…

  • Your Role Hierarchy Is Probably Lying to You

    —

    by

    Kevin
    in

    Most data platforms look clean on paper. Roles are defined.Permissions are assigned.Access flows in a structured hierarchy. It’s logical. Predictable. Auditable. At least, that’s the idea. In reality, the access model you think you have and the access model you actually have are more than likely two very different things. And the gap between them…

  • Most AI Initiatives Don’t Fail for the Reason You Think

    —

    by

    Kevin
    in

    Over the past few weeks, I’ve been writing about a pattern I’ve seen across a lot of data platforms: AI initiatives start strong… and then stall. Not because of talent.Not because of tooling. Because of architecture. Across different organizations, the pattern is surprisingly consistent: In fact, they’re the default path for many teams. But when…

  • From Legacy to AI -Ready: A Practical Modernization Roadmap

    —

    by

    Kevin
    in

    Part 5 in a series on evolving SQL Server environments into AI-ready architectures. Once organizations recognize the architectural gap between traditional platforms and AI workloads, and understand why lift-and-shift migrations fall short, the next question becomes practical: How do we move forward without disrupting the systems that already work? For most teams, the answer isn’t…

  • Where SQL Server Meets AI: The Case for Hybrid Architecture

    —

    by

    Kevin
    in

    Part 4 in a series on evolving SQL Server environments into AI-ready architectures. Simply moving SQL Server to the cloud isn’t enough. Lift-and-shift migrations reproduce the same bottlenecks — often at higher cost. The friction between traditional platforms and AI workloads persists. The solution isn’t abandoning SQL Server. It’s placing workloads where they belong: a hybrid…

  • The Lift-and-Shift Migration Trap (and Its Hidden Costs)

    —

    by

    Kevin
    in

    Part 3 in a series on evolving SQL Server environments into AI-ready architectures. Once organizations recognize the architecture gap we discussed in a previous post, the natural instinct is often straightforward: “Let’s move the warehouse to the cloud.” Databases migrate. Pipelines move. Infrastructure changes. The environment is now technically modernized – cloud-based, scalable in theory, and…

  • The Architecture Gap Slowing Down Your AI Strategy

    —

    by

    Kevin
    in

    Part 2 in a series on evolving SQL Server environments into AI-ready architectures. In the previous article, we talked about a pattern many organizations are experiencing: AI initiatives begin with excitement… and then quietly stall. Not because the teams are weak.Not because the use cases are flawed. But because the underlying platform was never designed…

  • AI Isn’t the Problem – Your Platform Might Be

    —

    by

    Kevin
    in

    First in a series on evolving SQL Server environments into AI-ready architectures. I see it all the time. Strong SQL Server teams.Stable production systems.Clean governance. Then leadership says, “We need AI.” A pilot launches. A model shows promise. Excitement builds. And then progress slows to a crawl. Not because the team failed. Not because AI…

  • Blueprint for AI in Snowflake: How to Scale Intelligence Without Burning Down the Warehouse

    —

    by

    Kevin
    in

    Because “just add AI” is not a strategy. It’s a dare that can go very wrong. Let’s Recap the Tour Over this series, we covered: Now it’s time to tie it all together into something usable. Not hype.Not vibes.Not “AI transformation journey.” A blueprint. Cue This Must Be the Place (Naive Melody)Because if you’ve done this…