T-SQL Tuesday #204 – Are blogs still relevant? (Roundup)

I did not expect 27 responses to my T-SQL Tuesday #204 invitation, but it appears many folks had a lot to say about whether or not blogs are relevant. I was excited to see posts from my friends, from folks I deeply respect, and from folks who I don’t know but who’s blogs I am glad to have now discovered. Thank you all for responding!

Interestingly, the posts didn’t all appear to say the same thing, although there were some commonalities. As expected, I found the responses to “Are blogs still relevant” to fall into three categories:

  1. Yes
  2. Yes, but…
  3. No

However, the discussion of motivation for writing blogs, as well as reading blogs, was varied across all responses. Most importantly, nearly all the responses were thought provoking.

These summaries are ridiculously oversimplified, but with so many of them I wanted to keep this post shorter than a Tolstoy novel. Here they are, with some sample quotes. Thank you again to all who participated!

The roundup

Aaron Bertrand provides a host of reasons why blogging is still relevant. Perhaps the most obvious is the academic gains from showing your work.

If you’ve worked through a problem, reconsidered some advice, challenged long-standing techniques, or found a way to explain something that finally made it click, you probably have something worth writing down, too.

Alexander Aarvidsson encourages folks to write the post they would want to read, especially because of all the AI slop posts.

Here’s the thing: the format didn’t change. The signal-to-noise ratio did. That makes the personal, real content more valuable, not less. A blog is relevant when the person behind it is.

Andy Brownsword acknowledges the proliferation of LLMs, but says the value in blogs like in sharing the experiences – including the gotchas.

They’re a distribution channel which can readily answer factual questions, but when asked why, their insights can only go as far as the experiences we share.

Andy Levy notes the freedom of writing blog posts vs creating other content, as well as the convenience of finding info from former posts from bloggers he follows.

I can’t tell you how many times I’ve said “I need to do this task. I know so-and-so has written blog posts about it” and off I go to my search engine to find those blog posts – I just look for “<name> <topic>”.

Andy Yun shares that he’s been feeling a bit burned out, but on reflecting about his own blog that dates back to 2013, feels inspired by the personal value of writing about learned experiences.

But as I sit here reading my early entries, I am also reminded that a blog can serve a much more personal purpose. It is a written history of my own career and personal journey. The blogs I’ve written are a reflection of me at that point in time of my life.

Brent Ozar follows up my questions with more questions, and oberves that even though there are less blogs now they are no less relevant.

The world is moving faster – but that doesn’t make blogs less relevant, it makes them more relevant since it’s one of the places you can find hot takes on this new stuff.

Chad Callihan emphasizes that writing blog posts can help your career beyond your resume. The can help at your current job when you are telling your coworkers (or clients, which Aaron Bertrand also noted) about a post you wrote.

I’ve had occasions where an issue or specific SQL Server feature was brought up in conversation, and I could say, “I researched and wrote about that, which you can check out here.” That’s a unique way to leave an impression.

Kevin at Chantified Lens feels writing blog posts allow us to share views and “get creative” in ways other platforms can’t.

I firmly believe blogs are still relevant. Even though AI is able to do a lot of work these days and assist greatly, there needs to be creativity for some solutions, and AI will never replace your personal point of view about topics.

CuratedSQL, Kevin Feasel’s “blog” that shares posts from nearly all the others here, provides an even more succinct summary than this post. But with added cheekiness.

In short, this might amaze you, but most bloggers think that blogging is still relevant.

Deborah Melkin ponders a bigger question: are blogs or something else the best way to reach our community of fellow database enthusiasts?

The problem is reaching people. It used to be through social media, but that has become fractured where everything is so spread out. Then it was user groups and SQL Saturdays/Days of Data/etc. Attendance for some of these is down or still looking to be revived. Most of these are homegrown without support of major organizations, so how can we make these things seen again?

Gethyn Ellis admits the benefits of writing blog posts as a consultant, sharing a story that is practically the reverse of my interview experience I noted in the invitation post.

When I started the consultancy, I had no established business reputation, no sales team and no collection of client case studies. The blog gave people something concrete to judge me by. A potential client could read my posts and decide whether I understood the problems they needed help with.

Hila Galapo points out the obvious reasons for writing blogs, but as a reader she’s discerningly looking for something an LLM likely won’t give you.

I read blogs of people who can tell me a story and can interest me with the challenge that they had, even if it’s not something that I’m facing right now. I believe that when I read something it would probably be useful somewhere in the future.

James Gallagher enjoys the community aspect of blogs, which can be sorely missed for remote workers.

Blogging and being a part of the online community help fill some of that gap. When someone writes a detailed post on a topic I care about, I learn more about how they think than I would from a conference talk or a LinkedIn post. Blogs are tangible artifacts, something I can share, reference and find again a year later.

Jeff Mlakar takes the dissenting opinion to say that, for non-consultants, blogs are not worth the time or effort unless you are writing for yourself.

But when was the last time a hiring manager pulled up your blog and read three posts to vet you? They’re busy. They skim your resume, maybe your LinkedIn, and decide whether you’re worth a phone screen.

Lee Markum adds that writing blog posts not only force you to think, but the act of maintaining a blog can bring additional skills to knowledge seekers.

When I started blogging years ago, I had to learn something about web hosting and WordPress. When I recently moved my blog to an Azure Static website, I was exposed to all kinds of things I wouldn’t have ever looked at otherwise. For example, that move is forcing me to learn Markdown, which can be useful in other scenarios too!

Louis Davidson, who manages Redgate’s Simple Talk site, had an amusingly succinct answer to the question of blog relevance.

I clearly hope so.

Mala Mahadevan enjoys the original writing of blogs as both a writer and a reader.

Original writing and original voices have their value and their place, and always will. I think blogging should stay as long as original thinking and writing should. Which is, always.

Marlon Ribunal remarks that LLMs aren’t entirely the enemy of blogs, and that they can be used them to help write better blog posts, helping with organization, grammar, and writing test scenarios.

Now we have AI tools that can help organize our thoughts, improve sentence construction, check grammar, and make an article easier to read. That doesn’t mean we should let AI do all the thinking for us. We still need to bring our own experience, technical knowledge, research, and judgment to the table.

My boss Mike Walsh comments on the advantages and disadvantages of learning via blogs (or encyclopedias!) vs using an LLM to get a quick answer.

But when you take that answer you:

  1. Don’t learn.
  2. May break something…
  3. …You don’t develop troubleshooting skills.
  4. Don’t build context for the pros/cons and ifs and whens.

Niko Neugebauer also thinks blogs are not directly relevant today, although he admits that deep down they are – to humans and to AI.

For most readers, probably not as a first stop: they’ll ask an LLM or watch a video. But those answers are built on what someone took the time to write down. I’ll keep blogging, even though on paper – logically, commercially, and in terms of reach and impact it makes little sense. And that is the very reason that makes me human.

Rebecca Lewis enthusiastically writes that blogs are “absolutely!” relevant, and that she loves the interaction in the comments section.

That’s another reason I value technical blogging. We don’t just share what we know. We learn from one another. I really think that is the biggest point right there — we learn from each other.

Reitse Eskens asserts the process of thinking, questioning, and getting feedback in blogging has not been replaced by LLMs.

For instance, if an AI tells you to run DBCC FREEPROCCACHE, DROPCLEANBUFFERS. Will you believe this is essential? Or will you check what this does before running it. And, will you read this differently when there’s a whole explanation around it why it was necessary in the specific situation this blogger was writing about.

Rob Farley maintains that although blogs are not as popular as they were in 2009, they can still help your career.

A candidate may never get asked about whether they write a blog, but the interviewer (or AI agent!) searches for the candidate online and finds the blog, then they can get an idea of who the candidate is ahead of time. Maybe this will bump them up to the top of the pile.

Shane O’Neill ruminates that writing a blog comes down to three things: recognition, awareness, and technical currency.

I don’t know if blogging is still relevant. I’m still going to do it. Slowly. Incrementally. Fighting imposter syndrome, burnout syndrome, laziness syndrome, and all other sins and/or dromes with every keystroke and backspace.

Shawn Oden recalls how much he has learned from blogs over decades, and suggest that good blog content is still valuable in the era of LLMs.

You probably won’t get as many direct subscribers to your blog as you used to. It’s just too easy to ask whatever flavor of LLM you prefer to help you with your issue. But it’s those good blogs that allow those LLMs to give you the good answers. Otherwise, if the LLMs never get new content to learn from, you just keep getting the same stagnant slop.

Steve Jones announces that Mike Walsh and I will be handling stewardship of T-SQL Tuesday (no pressure!), but then pivots to providing a short list of what blogs he enjoys.

Keep blogging, and keep reading blogs. It’s good exercise for your mind, and it’s a great way to improve your communication skills.

Vlad Drumea mourns the loss of readers to his own blog, but says that’s not going to stop him.

The stat counter is a terrible reason to write and, increasingly, an unreliable one to measure by. The things that made blogging worth doing in the pre-AI summary era, trading war stories with people who do the same job, still work in 2026. They just don’t show up as neatly in a chart.

T-SQL Tuesday #204 – Are blogs still relevant?

Note: This post is the invitation for T-SQL Tuesday #204 on November 3rd, 2026. If you’d like to reply, your response should go live on November 10th, 2026. All posts must be posted by 23:59 Pacific Time. Details and the rules are at the bottom of this post.

In 2009, right around the time T-SQL Tuesday was getting started, I wasn’t a very good at SQL Server. I could install it, check some boxes, and restart the server if there were problems. But that was about it.

That year I found myself looking for my next job as a Database Administrator. I went to an interview with a large healthcare company all ready to answer technical questions and give reasons why they should hire me, and the interviewer starts by asking me: “What SQL Server blogs do you read?”

I was frozen, because I didn’t read any database blogs. I didn’t even know there were such things. I read blogs about sports or music or any number of frivolous things, but nothing then that related to databases or SQL Server. I blurted out something about “Microsoft blogs” and continued with the interview, a bit shaken. Ultimately, I didn’t get offered the job.

But that question haunted me so much that afterwards I started seeking out blogs, and later other forms of media produced by people in the data community. That sharing of free information in blogs has made a massive difference for my career path. Obviously, at some point I started my own blog, which I dare say has made a significant impact in my skills and employment.

But…have times changed since 2009? Are blogs still relevant?

The invitation

For this T-SQL Tuesday, I’m asking folks to share why they do or don’t think the blog platform is still relevant for those of us working with databases.

I realize it’s a bit odd to ask folks to write a blog post about the relevance of blogs, and how that might tilt the resulting content, but I also know there are a lot of folks who have lapsed in their blogging in recent years. I’m wondering if that’s an issue of being too busy, or not having enough to say, or just not being interested in this medium anymore.

There are no wrong answers. You can talk about your favorite reasons for blogs as either an author or a reader, or even share a short list your favorite blogs and their reasons for relevance to you.

Conversely, you can talk about alternative media you use to learn about all the new things. Or even respond on an alternative medium and link it here (which might be a first for T-SQL Tuesdays). Or, if you have lapsed in blogging and reading blogs, share the reasons. Heck, you can even reminisce about “the good old days” of…whatever you think made up the good old days of blogging.

The “rules” (don’t worry – like the Pirate Code these are more like guidelines)

T-SQL Tuesday is a monthly blog collaboration of sorts started by Adam Machanic and maintained by Steve Jones, and everyone with a blog is welcome to join. Here’s how to play along.

  • Publish your post on Tuesday, November 10, 2026 between 00:00 and 23:59 UTC on that day.
  • Include a link back to this blog post, or leave a comment in this post linking to your content. (This one is actually a rule.) 
  • Please include the T-SQL Tuesday logo at the top of your post.
  • Share it on social media with #tsql2sday so the rest of the community can see it.
  • Any blogger is welcome to participate. It doesn’t matter how long your blog has been active, where you blog, or even what language you post in. We just want to hear your thoughts.

One week later I will publish a “roundup” post linking to all the responses. I’m greatly looking forward to this, and I hope you have some fun with your response – this is a request for a voluntary contribution, not homework.

Thank you in advance for sharing your thoughts on this subject. T-SQL Tuesday has been connecting bloggers and helping to bring awareness to new authors since 2009, and I certainly hope that continues this month!

T-SQL Tuesday #193 – A Note to Your Past, and a Warning from Your Future

I haven’t posted in a while (well, not here at least since I’ve been posting at the Straight Path Solutions site recently), but I did want to reply to the latest T-SQL Tuesday call. This month’s edition is hosted by Mike Walsh, who asks folks to write two short but thoughtful notes to yourself: one to your past self of 10 years go, and one from yourself 10 years in the future.

One quick note: am I writing this to myself? Absolutely. But hopefully these words resonate with others not as far down my path, as I’ve learned these truths the proverbial “hard way”.

Continue reading “T-SQL Tuesday #193 – A Note to Your Past, and a Warning from Your Future” →

What I’ve learned in my first 100 days with a consulting group

In case you don’t follow me on LinkedIn or Twitter, your humble host joined the smart folks at Straight Path Solutions in March. This is a talented group of SQL Server consultants founded by Mike Walsh and includes several former Microsoft MVPs, and I’m incredibly honored to be part of their team.

Especially since I didn’t have much experience as a consultant.

Maybe you don’t either, which is why I wrote this post. If you ever wanted to know how consulting is different than a typical job as a fulltime DBA, I’ve assembled this brief retrospective of things I’ve learned so far.

Let’s get to it then.

Continue reading “What I’ve learned in my first 100 days with a consulting group” →

How to find tables with 0 records using space

This is a follow up post to the previous one about tables with no records using data space, with the idea coming from twitter of all places. Sometimes on twitter the conversations kill, but after reading that post my friend Chris Wood suggested writing something to FIND those tables.

Which is a solid idea, so let’s get to it. No time to wait too long.

Continue reading “How to find tables with 0 records using space” →

How can a table with 0 records use so much space?

Just like that puppy you got during the pandemic, your databases hunger for more. And they grow. And occasionally make a mess. I’ll stop the analogy.

Anyhow, it’s worthwhile to occasionally review the tables in a database to see which ones are growing every day, using the most space.

But what if during a review you see the largest table looks like this?

That’s around 24 GB of sweet drive space allocated for 0 records. But…how?

Let me show you how.

Continue reading “How can a table with 0 records use so much space?” →

How to get Change Data Capture to work in an Availability Group

If you’ve ever had to implement Change Data Capture (CDC) for a database in an Availability Group, then you know that the CDC jobs don’t really consider the Availability Group. The capture and cleanup jobs created are set up as if the database exists only on a single instance.

And that’s a problem, because I would guess quite lot of databases are in Availability Groups. Maybe even some of yours. If you have this issue, I’ve put together a step-by-step solution in this post.

I know this post is a little long compared to others here, but I’ve tried to be thorough to save you headaches.

Continue reading “How to get Change Data Capture to work in an Availability Group” →

sp_GetRowcount: How to count the number of rows in any SQL Server table fast

Have you ever had to find the number of rows in a user table, and then wrote a little “SELECT COUNT(*) FROM tblWhatever” and hit execute…and waited…and waited…and waited some more? And then started wondering what was going on?

If so, this post is for you.

Let me explain the problem, and then give you a reusable solution. Consider this a turning point in your career.

Continue reading “sp_GetRowcount: How to count the number of rows in any SQL Server table fast” →

How to tell if Change Data Capture (CDC) is working as expected

I’m not sure how many of you use Change Data Capture (CDC) on your instances, but I’ve had to support it for a while now and I thought I’d share a little script I use fairly frequently to help troubleshoot the capture and cleanup, as well as some advice for resolving issues.

Sharing is such a gentle trait.

Continue reading “How to tell if Change Data Capture (CDC) is working as expected” →

#TSQL2sday – Preconceived Notions About Who Is Smart

For this month’s #TSQL2day, Andy Yun asked folks to share about “something you’ve learned, that subsequently changed your opinion/viewpoint/etc. on something.”

Now, there are technical subjects I could share where I’ve changed my opinion, but in thinking about possible answers I realized all of them start with one thing that has changed: who I thought was “smart”.

I put the word smart in quotes, because it’s a totally subjective and ever-changing opinion. Let me show you what I mean.

Continue reading “#TSQL2sday – Preconceived Notions About Who Is Smart” →