Voice of the DBA

Author: way0utwest

  • Enterprise Software

    “I’ll go in the store; it’s built for that.”

    That is a quote from Jessica Kerr, who is a developer. She has a great blog on software development, called The Enterprise Eats Software. It starts with a poor experience for an online order for Lowe’s. Interestingly enough, as I read this, I was starting a home renovation project, but I didn’t have a bad experience, I had a great one. Read Jessica’s blog, and see what you think.

    For my short story, we had contracted for a bathroom project, but we forgot to get some of the fixtures. The contractor came a day early to talk about things, and we realized we needed a shower diverter valve and trim kit. We looked for the trim, which is what was important to my wife, and found a valve to fit it. While the contractor called two local supply houses, I looked at Amazon. The suppliers didn’t have the valve, but Amazon did, noting delivery in two days. I ordered it around 10:30 am that day. It arrived around 11:00 am the next day, a day early and before the existing shower had been demoed.

    That was fantastic. It made me think why would I want to use any service that wasn’t that amazing and quick. I got an email at my desk with a picture, telling me the package had been delivered and showed me where it was. I walked it upstairs thinking that calling multiple suppliers and then driving around town would have been a pain,  not to mention a time sink.

    I don’t often find a lot of large companies do a good job with their software integrating into real world operations. A few do, and apart from Amazon, I’ll say build.com was incredible for us to get a tub and Wayfair got us a vanity very quickly (too quickly, actually). Both have built great systems that not only took the order but updated us and handled the complexities of shipping large items. Not to mention they both had an incredible selection available to peruse easily and quickly. Just finding a place to look at something like a tub in person is incredibly difficult.

    Apart from the retail challenges, just the general experience from many enterprises leaves something to be desired. They just aren’t good at being agile, flexible, and maybe more importantly, constantly improving. They get caught up in some of the hassles, like bureaucracy, power struggles, too many rules, etc. They don’t know how to operate in a flexible, agile, constant change environment.

    I’m reading Project to Product, which in many ways sees a lot of the same problems. Software is disconnected from the goals of the business, and too often there are individuals and processes that get in the way of becoming more effective across teams and partners. BMW is one of the success stories here, and I still think they’re behind Tesla in their industry. They might catch up, and if they do, it’s because they are learning to be a better software company, not a better manufacturer.

    Steve Jones

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

  • Daily Coping 12 Jul 2021

    I started to add a daily coping tip to the SQLServerCentral newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m adding my responses for each day here. All my coping tips are under this tag. 

    Today’s tip is to look for something positive in a difficult situation.

    My life is mostly great, and I feel strange complaining or getting upset about things. In general, my difficult situations are merely uncomfortable or annoying, and I try hard to remember that.

    Difficulties are relative, and for me, I had a tough time with a bunch of things breaking at home. During a busy time, with lots of other commitments, I needed to stop and rebuild a hub on a trailer. It gets used every day, and I had a choice between rebuilding the exploded one, or adding some supports and bracing to a 2nd trailer. Neither was quick.

    I was a little annoyed when I went out to see this, but then stopped to revisit how I looked at the situation. No one did this on purpose, it’s the way things go in the real world, and I know how to do this. While I was grumpy with a few people as I started, I managed to take a positive outlook on this as I got into it.

    I got to practice a few skills:

    • quickly removing the old hub bearing race with a specialized tool
    • grinding down the axle where it was slightly deformed
    • taking a break to get a new set of bearings
    • using my experience to reassemble the wheel in about 40 minutes
    • Not bending (too much) the hub cover tapping it back on.

    All in all not what I wanted for the day, but it was fine. I got a few other things done, and got to teach a few people how to prevent this in the future.

  • RIP Brian Moran

    When someone older than you dies, it’s sad, though I feel that I can cope. I hold memories dear, I appreciate the time I had with an individual, and I hope I can live as long as they walked the Earth.

    If someone younger dies, it’s truly shocking. After being stunned, I often stop and appreciate where I am in life, and that I’m still here.  A phrase runs through my head:

    There, but for the grace of God, go I.

    I’m not a religious person, but that phrase sticks with me. I am lucky to be where I am. I’m lucky to have had good fortune, and that my bad fortune hasn’t been catastrophic.

    Today I got a note from a friend. He told me that Brian Moran (t, st, mvp, li)  had passed away. Brian was a wonderful man, someone I’ve known close to 20 years. We worked in the same field, we were fellow speakers at events, and we’ve had numerous phone calls at times trying to find ways to work together in business. He was a big part of the PASS organization, of supporting SQL Saturdays, and helping grow the SQL community larger and stronger.

    He is one of maybe a few dozen people in my professional life whose partner I’ve met, who’s met my wife, who I’ve had talked with while at home, and who loved Hawaiian shirts like me. We have daughters the same age, and we’ve shared many conversations over the years. We weren’t that close, but we respected and enjoyed each other’s company often. One of the relatively few people I’d stop and have an extended conversation with when we were together.

    I have no details on what happened, and my heart goes out to his wife and family. It’s a stunning day, and as pat of my job, I’ll update a memory a sqlmemorial.org next week. One of the harder posts that I’ll have to write.

  • Do We Need to Learn Linux?

    This week we got an announcement about SQL Server in Containers. Microsoft put out a blog noting that the beta program for SQL Server on Windows containers is suspended. They didn’t give any details, citing “ecosystem challenges and usage patterns” as a reason so suspend the program for the foreseeable future.

    Not only that, they noted that they were deleting docker hub images for express and developer, which makes sense from their perspective. They don’t want to support these. From the developer perspective, however, this will break and flow, pipelines, or even local scripts from developers. I understand the desire to delete images, but doing so without any notice doesn’t seem like fair treatment for people using them.

    This means that if you want to run SQL Server in a container in production, you likely have to use Linux. Windocks has an alternative with Windows, but Microsoft not supporting this is disappointing. I think that containers will be the future of database development, as they standardize and simplify how we can get an environment up and running. They also ensure consistent environments between developers, branches, automated systems and more. I think it’s going to take years, but that’s the direction where I think many of us will go over time. Those days of the Developer Edition will be gone, and instead we’ll just run a container.

    I’ve been using Linux containers for a few years, and they make it easy to quickly set up a clean environment with a new instance and a database or two. In that time, I’ve had to use a little Linux at times, but really, I start a container from a command line and then it acts like an instance I’ve installed. There isn’t a reason to actually do much in Linux. At least not for the core database stuff. Most of the ways that you’ll work with a Linux instance as a developer stay the same.

    For system administrators and DBAs, however, you might need to learn more. While setting up an instance on Linux isn’t hard, and easier in a container, if you are called on to work in bash, execute sudo, or some other Linux command, you might want some basic familiarity. Fortunately, you don’t need another workstation as Windows 10 includes a Windows Subsystem for Linux (WSL) that let’s you play around in Linux inside Windows 10.

    I think Linux is fascinating, and it’s evolved in many ways since I first saw it in 1991. Even if it’s not something you expect to use daily, spending a few hours learning how to navigate around and get things done is good for your mind, forcing you to learn a bit. The San Diego TIG did a series a few years ago, and you might go through those meetings or pick up a book and spend some time playing around with something new. You never know when this might be required in your career and a little familiarity could give you a jump start in the future.

    Do we need to learn Linux? No, but it’s not a bad idea to build a few skills in this area.

    Steve Jones