It’s time for T-SQL Tuesday again! And we’re almost to number 200! T-SQL Tuesday is a monthly community blogging event started by Adam Machanic in 2009. Each month a host picks a topic, participants write about it on the second Tuesday of the month (9th of June), and the host posts a recap with links to all the responses.
I was intrigued by this blog post from Alexander Arvidsson (blog | bluesky | linkedin): The Whiplash Effect – The Skills We Forgot We’d Need. He talks about the fact that more and more clients are considering moving back to on-prem. Or at least consider it an option when brainstorming architectures. There might be many reasons for this (and it might be a Europe thing, who knows), such as cost, performance or political climate. Alexander then poses the questions: do we still have the skills to create an infrastructure and data platform on-premises? Haven’t we lost too many skills after a decade of cloud computing? When was the last time you had to deal with a slow SAN? (it’s always storage. And if it isn’t, it’s DNS) Or had to set up Kerberos? Or had to deal with file paths that were too long for Windows to handle?
So, dear reader, I want you to think about what would happen if suddenly your company or your client asks to build everything on-prem again (or maybe a hybrid architecture). Possible angles can be:
A week later, I’ll post a roundup of all participating blog post on this site. If you’re interested in hosting a future T-SQL Tuesday, contact Steve Jones at tsqltuesday.com/requesttohost.
I’m looking forward to your contributions!
A while ago we suddenly had an error while trying to deploy one Fabric workspace…
I've uploaded the slides for my Techorama session Microsoft Fabric for Dummies and my DataGrillen…
I'm doing a small series on indexing basics for SQL Server, and on May 14th…
A short blog post about an issue with Fabric Mirroring (with Azure SQL DB as…
I'm starting a webinar series about SQL Server indexing with the fine folks of MSSQLTips.com.…
A while ago I blogged about a use case where a pipeline fails during debugging…