← Back to Insights An Old Dog's New Tricks — Part 1

I Asked AI to Write SQL After 30 Years of Doing It Myself

Ken Whiteside July 2026 4 min read

I've been at the beginning of things before.

Novell replacing the VAX room. SQL Server when it was command line only. Building networks out of parts on my kitchen table.

I know what "early" feels like. And AI is it.

But here's the thing nobody tells you about being early this time: it's humbling.

I've been writing SQL for 30 years. I'm good at it. Fast. I know the patterns, the edge cases, the "don't do it that way" lessons you only learn by breaking production at 2am.

So when I first asked AI to write a stored procedure for me — one I could have written myself in 20 minutes — I wasn't sure why I was even doing it.

Then it came back in 8 seconds. Correct. Clean. With error handling I would have added later but it included from the start.

That felt... weird.

Not bad. Just weird. Like watching someone else drive your Vette at Road Atlanta and realizing they're hitting lines you didn't know existed. I didn't know what I didn't know until I saw things happen I didn't think were possible.

My first instinct was to find something wrong with it. Pick it apart. Prove I still mattered. And honestly? I found a couple of things. Business logic nuances it couldn't have known without context. A join that was technically valid but wrong for our data model.

That's when it clicked.

AI didn't replace my 30 years of knowledge. It just made the typing part irrelevant. The THINKING part — knowing what's right, what's wrong, what the business actually needs — that's still mine.

I'm not writing SQL anymore. I'm directing it. Reviewing it. Correcting the 5% that requires human judgment. And I'm doing it 10x faster.

I'm lucky to be at a company that's pushing us to adopt AI, not resist it. That makes all the difference. When leadership says "go learn this, use it, show us what's possible" — it removes the fear and replaces it with opportunity.

Here's what I wish someone had told me on day one:

You're going to feel threatened. That's normal. Push through it.
The first few times will feel slower (you're learning a new workflow). Keep going.
Your domain expertise is what makes AI USEFUL. Without you, it produces plausible garbage.
Start with something you already know how to do. That way you can validate the output.

If you've been doing data work for years and haven't tried letting AI generate your SQL, your ETL, your DDL — try it this week. Just once. See what comes back.

You might be surprised. And a little uncomfortable. That means it's working.

That was a few months ago. Since then, I've connected AI to every system I touch, cut ticket cycle times by 60%, and completed tasks in 30 minutes that used to take 3 hours. But it all started with that one uncomfortable moment of letting go.