By Riley Major, 2018-03-13
These days, most business logic is still built by subject matter experts. Humans explore their habits and instincts and try to come up with a process which business analysts turn into an algorithm which developers turn into code. That’s expensive, time consuming, and is all based on the presumption that computers need to be told what to do.
For the 99th T-SQL Tuesday (that’s over 8 years of blog parties), Aaron Bertrand invites us to write about our #sqlibirum (credit to Drew Furgiuele and Melissa for the term)– our passions outside of SQL Server and technical community.
These days, aside from my family and technology, I’m putting most of my energy into learning more about the privileges I enjoy in society and how to dismantle the systems which provide them. Twitter has exposed me to ideas and realities which I’ve never had to face in the past, and it’s frustrating to learn about how stacked the deck is against so many people. That said, except as those issues intersect with technical communities, I’m not ready for this blog to become overtly political. So I’m going to take Aaron’s escape pod and talk about a T-SQL bad habit.
For this month’s T-SQL Tuesday, James Anderson asks us to write about Shipping Database Changes.
These days all the rage is continuous deployment. Once development is “complete”, you push a button, (insert automated process here), and boom, the code is in production. I applaud shops which can reach this stage. It requires extreme devotion to automated testing and scripted processes. I haven’t worked with that sort of a system. However, many of the same principles apply to deploying the old fashioned way. Continue reading
Kennie Pontoppidan hosts this month’s T-SQL Tuesday and asks us to write about “the daily (database-related) WTF”. I will admit that occasionally I submit to Schadenfreude. And when I get stuck cleaning up someone else’s mess, my hindsight is 20/20. I can point out all the problems they were too “ignorant” or too “lazy” to fix. And then I remember that “they” was “me”. Continue reading
Matt Gordon hosts this month’s T-SQL Tuesday and asks us to write about how we’ve used a new capability of the SQL Server ecosystem to solve an old problem. At first blush, this seems like a good way to show concrete benefits to abstract new concepts. But I wonder if it sets the bar too high. Continue reading
I have to admit, I’ve been pleased with the developments with SQL Server 2016. In addition to all of the new features, they brought SQL Server to Linux and with SP1 they opened all the goodies up to Standard Edition. So when Brent Ozar asked us to scour Microsoft Connect for even more improvements for T-SQL Tuesday #86 (#tsql2sday), I wondered if we wouldn’t tempt fate. But as IT folks we love to complain about our tools, so here goes. Continue reading
Andy Mallon hosts this month’s T-SQL Tuesday, asking us to reflect on Allan Hirt’s tweet lamenting that “we’re still dealing with the same problems” after 25 years in IT.
I think technology has the paradoxical problem of moving both too fast and too slow. Continue reading