AI Database Central

SQL Server Central has been a great success over the last 25 years. We’ve helped a lot of people improve their careers with the Microsoft Data Platform, primarily SQL Server, but we’ve published articles on other aspects of databases, including other platforms. I wrote a bit about the history of the site last month, with a few stories in various pieces. We even got Brian Knight to contribute a piece on what the site meant to him.

Over the years, we experimented with trying to get an SSIS Central or a SSRS Central off the ground. However, we struggled to find other people who would have been willing to partner with us to provide content and answer questions. Eventually, we gave up, though I wish today we’d have pushed forward with a PostgreSQL Central site a few years back.

However, we’re moving forward with AI Database Central next week. This is an experiment that will look to gather lots of articles and news on how AI technology can be used to work with databases. Our goal is to build a site that showcases some of the ways in which AI works well. To handle the load of producing articles, we’ve got a very modern take.

We’re setting up a Clawdbot system that will read existing articles and questions and then produce its own articles based on the knowledge of what AIs have about database technology. For every article here on SQL Server, we’ll get a series of articles that cover the same topic on Oracle, MySQL, PostgreSQL, and MongoDB to start. We’ll turn the AI agents loose on more platforms over time, but our hope is that this will provide an exhaustive body of knowledge that other data professionals and AI agents can use. We’ll even have an MCP server available.

Of course, we will take submissions, which AI agents will edit and provide feedback. We’re also looking to experiment with submissions of editorial topics and ideas, which the AI agent will then use to produce its own content for you to read.

This will likely not work that well, mostly because it’s April 1 and this is an April Fools joke. It could be possible, couldn’t it? Not likely very good, but it could be fun.

Steve Jones

Listen to the podcast at Libsyn, Spotify, or iTunes.

Note, podcasts are only available for a limited time online.

Posted in Editorial | Tagged | Leave a comment

Finding Balance: Things Will Come Up

I have a presentation on finding balance in your career that got quite a few people thinking and commenting on their own experiences. I decided to write a few posts supporting the ideas in the presentation, which my wife and I have used to both drive our careers forward while enjoying our lives.

Just this week, I had an example.

This is a series of posts on finding balance in your career.

It Starts with a Picture

My daughter told me this happened Monday afternoon. This is one of our horse feeders, and as you can see, the bottom has fallen out.

2026-03_0141

This happens periodically, but it was unexpected. In this case, I’d returned from a week and a half of travel, and I needed to try and get prepped for some additional travel the following week.

In other words, I had plenty of work to do, lots of commitments in life already in place, and now something new pops into my life.

This isn’t critical, but it is something I need to get done before I leave again, which left me limited time around work, coaching commitments a few nights a week, trying to get time to exercise to maintain my health, cooking for the family while I’m here, and, of course, getting time to relax.

I decided I’d have to find time in a couple ways. First, I got up a little early, 30 minutes, the next day and started working. When my daughter texted that she was getting the tractor out, I took a break and went outside to meet her and bring the feeder back to the house.

I then evaluated what was needed and realized I needed some wood from the hardware store. Fortunately, I had a meeting scheduled that I didn’t need to speak in, so I started to town while listening to the meeting in the car.

Multi-tasking FTW.

I had almost completed my trip to town when the meeting ended. I drove back and went back to work, handling a few tasks, editing an article, etc. Once I thought I had gotten most things done for the day, I took a break.

It took about 75 minutes to cut some wood and re-attach the pieces and parts in the feeder. I’d cut into my day a bit, but fortunately work is flexible and I can work a little longer on Wednesday to make up for the time missed.

That extra work will cut into my time to relax, but this is an unexpected issue, and I have to trade time somewhere. Making adult choices, I flexed work to get something in my life done sooner, and spread that flex across two days so that I wasn’t overloaded.

Less time to relax, but that happens some weeks. Especially with horses.

Posted in Blog | Tagged , , | Leave a comment

Prompt Requests

One of the challenges of AI-assisted coding agents is that they tend to produce A LOT of code. Even in refactoring or migration changes, the AIs can work quickly and generate such a volume of code that the process starts to become overwhelming. For pull requests, for CI/CD build systems, and certainly for human reviewers, they can be overwhelmed. This can become a real problem with OSS projects, where submissions can grow exponentially to the point that maintainers stop looking at pull requests. I suspect the same thing might happen in corporate repositories when lots of developers can refactor or submit huge amounts of code produced by AI agents in a fraction of the time it took a year ago.

I was listening to an interview with an experienced software developer and OSS project maintainer who said that he preferred getting a “prompt request” that contained a description of a problem and the specification for a solution that he could submit to his own LLM to get the code. Rather than use an AI to review a code in a PR written by a human or AI agent, a great prompt that can communicates the problem and solution is preferred.

That’s a fascinating idea to me. Specify what you want and let the code owners send it to an AI and get a code response whose quality and focus they can decide to implement, based on their own context provided to an LLM (standards, style, patterns, etc.)

Of course, for open source projects, perhaps the maintainer doesn’t want to spend time managing AI agents or working through quality, but this does allow them to focus on the idea being suggested rather than attempting to review code, test it, judge the quality, and perhaps request changes from the submitter. They can take your idea and implement it. If it’s a simple fix, even better, as the maintainer might get quick help from an AI, using the style of code they are used to (their own).

Software engineering is changing a lot in the age of AI, and this seems to be one of the more interesting things I’ve seen suggested. Not YOLO or vibe-coding, but rather a prompt that suggests the idea and turns contributors into a specification written for the robot coder.

Steve Jones

Listen to the podcast at Libsyn, Spotify, or iTunes.

Note, podcasts are only available for a limited time online.

Posted in Editorial | Tagged , | Leave a comment

Finding the Next Sequence Value: #SQLNewBlogger

I saw a question asking about the next sequence value and decided to try and answer it myself. I assumed this would be easy, and it was, but I used some AI help to make it very quick to get the value and learn something.

Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers.

Checking for Sequences

I know I’ve done some testing lately with sequences for a customer, so I decided to ask Prompt AI to help. I connected to a database and asked this question after clicking ALT+Z.

2026-03_0133

I got this response, which I executed before accepting the code. One thing I like about SQL Prompt is I can execute code and then adjust my prompt (or paste in an error). As you can see, I have 3 sequences in this database. I get a bunch of the meta data, including the current_value.

2026-03_0134

However, is that the next value or the last one? It could be interpreted multiple ways. I could look this up, but I decided to ask again. I accepted the code, then wrote a quick SQL statement to get the next value. If you’ve never done this, you might not know how sequences work, which is a different issue. In my case, a “se” tab, “ne” tab “i” got e this code. I then asked to find this.

2026-03_0136

SQL Prompt AI returned this query, which gets me the current_value, but I know that. I decided to ask for an explanation rather than Google or work my way through MSLearn.

2026-03_0137

The explanation is good. It’s not the current value + 1 it’s the current value + increment, which is a subtlety that some people might miss.

2026-03_0138

Let’s test this. I wrote some code and then executed it. I get 17, which makes sense. The current value (seen above) is 15 and the increment is 2.

2026-03_0139

Problem solved. This short session likely will help me remember this detail for future code (or prompts).

SQL New Blogger

This post took me about 8 minutes to setup the code, capture the images, and write this up. I’ve done a lot of these, but I showed how to investigate a question, use AI for help, and then make sure the AI is actually giving me something good.

You could write these types of posts and show your fluency with both data engineering and AI assistance. Take a minute and start writing some blogs that showcase how your skills and career are growing.

Posted in Blog | Tagged , , | Leave a comment