It’s time to celebrate and confess.

I was honored to host the June 2024 edition of T-SQL Tuesday – #175! That’s the celebration.

Confession: I had GoDaddy add a firewall back in February and it worked well. Too well, in fact! A friend reached out to let me know comments on the blog post – titled T-SQL Tuesday #175: Old Tech, New Tech, Bold Tech, Blue Tech –  was returning a nasty ACCESS DENIED message:

I should have known. Comments on the blog had fallen off quite a bit and I did not know why.
Now I know why.

I got the issue sorted but I wonder how many of you responded to the T-SQL Tuesday and were unable to post a message.

If you do not see your response in this round up post, please comment on the original post. Comments are now accepted (Note: Comments do not appear right away, they are moderated). I will receive the comment this time!

And Now, The Roundup

Rob Farley [@rob_farley] of LobsterPot Solutions shares Ready or not, a post in which he describes his thoughts on the constituents of the decision to move to new technology or not to move to new technology. Two sections bear quoting, in my opinion:

“Small updates to systems come through so frequently these days that it feels like larger software changes have become rarer. If the system you use gets an update several times a year, then it’s less likely that the grass will feel greener somewhere else. Why would someone leave the Power BI platform when new features appear every month? If some other product offers an amazing feature, aren’t all the competitors likely to roll out their own equivalents? Whereas if upgrading from version 6 of something to version 9 is a large undertaking, changing to the competitor is much easier. Vendors know this and want us to be on their journey of frequent updates.”

And Rob’s conclusion:

“My perspective is that people should be ready to jump onto the train. Whether it’s being Fabric-ready, AI-ready, or real-time-ready, whatever – the steps to prepare for new technology are often helpful in their own right. Knowing the things that might need to change and understanding the patterns that work on the new system as well as the old – these are things that can get you ready to make the leap. Because one day you might need to jump whether you’re ready or not.

And if the train you’re on might start slowing down, perhaps it’s better to move sooner rather than later.”

I concur with Rob’s assertions quoted above, and the remainder of his (excellent) post.

Chad Callihan [LinkedIn, @callihandata] of Callihan Data categorizes his responses into “For Work” and “For Play.” In the For Work category, Chad writes:

“I could say, ‘we can upgrade and then we can do x, y, and z’ but it may not be worth the cost if those changes more or less only check a box.”

“In the For Work category, Chad makes an important point regarding the pace of updates:

But somewhere along the line, I read an article that said, ‘this is cool, but this will be the worst Apple Vision Pro ever created,’ and for some reason that stuck with me. Soon enough, there will be software upgrades and hardware upgrades that will put the initial version to shame.”

Conclusion

Thank you Rob and Chad for your responses!

Again, if you participated in this month’s T-SQL Tuesday and do not see your contribution included in this post, it’s my fault. Let me know of your contribution and I will add it to this summary!