Voice of the DBA

Category: Editorial

  • A Virtual Trip Down Under

    I had a great holiday last week, getting away from my home for the first time in months. It’s been an extra strange time for me as I usually have a number of personal and business trips I’ve taken by this time, but with the pandemic, I’ve been at home, like most of you. However, we managed to find a campground open, and we packed up the family, dogs, and horses for a week in the South Dakota hills.

    I’m back, and while I won’t be getting on an airplane, I am going to travel virtually to Australia this week for quite an action packed Redgate Streamed APAC Edition. I’m slightly disappointed that I won’t be able to shake hands with Troy Hunt, but neither will Damian Brady, Greg Low, or Hamish Watson. I was on stage last summer with those three, and I immensely enjoyed the experience.

    This year we’re holding the event virtually in the Australia time zone, so I’ll be working late afternoon and evening my time for the event on Thursday, July 2. Time zones certainly get strange when I do things in Australia, and it’s the one place I’ve traveled where I feel really out of place when contacting this side of the world. The last time I was there, I watched my daughter’s evening volleyball game as I was eating breakfast.

    I get to deliver a talk, and then I’ll settle in to watch everyone else and enjoy the other talks. All of these are expert software developers and data professionals, and I learn quite a bit from them on a regular basis. If you want to spend time later this week, register for the event and join me, wherever you are in the world. The one good thing with these virtual events is that we can attend them if they fit our schedule.

    I’m excited to talk DevOps, software development, and, of course, security with the incredible Troy Hunt. This is an exciting week back for me, but also a busy one as I prep for a look at the software challenges down under.

    Steve Jones

    Note: Podcasts paused this week as I have construction taking place at the house and nowhere to record.

  • Moar Azure

    There are a number of choices for working in the cloud, aka, renting resources, but there are three big choices: Azure, AWS, and GCP. These three dominate the cloud services, though arguably AWS and Azure are way ahead. All three have lots of services, and all three can likely meet your cloud or hybrid needs, even if you work in a regulated industry or government.

    This week there was a piece on the work Microsoft is doing to increase their capacity. Between the 0365 Office services, Teams for collaboration, and their regular PaaS/IaaS workloads, they’ve grown quite a bit this year with the COVID-19 pandemic. As they try to increase their resources, they’ve had people working round-the-clock to add new servers. I’m sure they are still using containers, but likely they are struggling to fill these with new hardware.

    They’ve also been adding bandwidth, which is a bit need between the data centers. I had no idea they have their own undersea cables, but apparently they do. I suspect Amazon and Google do as well.  There is a note that they’re also coding, trying to improve efficiency. After all, while you can throw hardware at a problem, many of us know that bad code can overwhelm those efforts. We see it in our jobs every day. I would hope that many of our organizations that might be depending on software more realize that better code is an advantage for us and our customers.

    I know Microsoft runs a lot of their own stuff on Azure, including development work, and they’ve had to reschedule their internal workloads as well as move other work outside of regions. I think that’s fine in many cases, but with different laws in different countries, I hope they’re extremely careful about what moves. Data sovereignty can matter.

    If you read through the article, it seems that Microsoft has learned a lot about adapting their work methods, both with people and systems, to meet the increased workloads. This is one area that I hope we see some detailed technical blogs, which might help others learn how to better manage their own resource challenges, or even learn to code better. While some of this might be proprietary, with the move to having many things open source, why not share ways to improve application resource usage.

    Steve Jones

  • Evaluating Life at Work

    One of the more interesting things that we do at Redgate is regularly ask workers to evaluate their environment. We use a company, called Thymometrics, and periodically employers as asked to rate various factors, both in terms of how important are they to us, and how satisfied are we. I tweeted the general dashboard, but essentially there are a series of sliders we use to rate things, between a max and min. No scale, just a visual choice of are things more or less important. Am I more of less satisfied.

    The range is factors are here:

    • Work Environment
    • Wellbeing
    • Salary
    • Benefits
    • Culture and Values
    • Giving Something Back
    • Leadership
    • My Manager
    • Personal Growth
    • Recognition
    • Redgate’s Purpose
    • My Team
    • My Role

    When I log in, I can see how I last set things. I can also reset everything to the middle and re-evaluate how I view the world. Usually I look through and see if I want to change my satisfaction. Rarely do I think that some part of my job situation has changed in importance. However, at least once a year I do reset things and start over.

    While I know plenty of people see this as a pain in the sitting part of the body to go through, I appreciate it. This lets me evaluate how I feel about my job situation, and about my company. I get to think for a few minutes about whether I am truly satisfied with my position and how I am treated by this organization.

    This is a somewhat formalized process. I checked with the team that looks at this and they get anonymized rollup of data, unless someone puts in a comment and asks for a reply. Even then, they don’t send the raw data to managers, but attempt to mediate if there are issues. It’s a good idea, and really, this is what I do and recommend for others.

    At least once a year I take a serious look at my employment situation, in conjunction with how my personal life is going and think about what I like and don’t. I think about my other options, and discuss this with my wife. Is this the best way to live my life? So far it has been every year, since I think I have one of the best jobs out there. That doesn’t mean I should assume there aren’t other options or ways that I might want to change my job.

    I think you should do the same thing yourself, at least once a year. Honestly evaluate your situation, ask others about theirs, and make the best decision for you. After all, you only get one chance to go through this life. If it’s not working, plan to make a change.

    Steve Jones

    Listen to the podcast at Libsyn, Stitcher or iTunes.

  • Why Billing Will Be Part of Our Job

    I am old enough to remember when many large corporations implemented chargebacks. Essentially, each internal department was charged for their usage of IT systems, similar to how we are charged in the cloud. It was a mess, and individual departments had to answer for excessive charges. I don’t know that any department ever lost service, but their shared of the IT budget was certainly discussed in management meetings.

    These days more and more of us are going to move systems to the cloud, and some of those systems moved will be databases. We may not move all our systems, but we will move some, and the ongoing cost of those systems is something that we will periodically be asked to justify. In the past, we rarely dealt with billing, usually just when specifying and procuring new hardware or requesting a VM.

    Moving forward, I can see us spending time every quarter, or likely every year, analyzing the resources we are paying for and then determining if we are overspending.

    Or, if you’re proactive, perhaps you’ll start looking at costs and performance, as Brent did, and try to write better code to reduce your outlay every month by more efficiently using resources. Have you built in-efficient designs? Are you pulling back too much data with SELECT * from a table or view? Are you building code that recreates the N+1 problem?

    We’ve known for years that writing good code to interact with databases can prevent scale problems and overloaded hardware, even with large workloads. Many case studies over the years show SQL Server backing extremely large databases and busy workloads. Multi-TB databases with thousands of concurrent clients are common these days, and often we find that workloads at clients would easily be run on existing hardware with some better code.

    For some of us, the refocus on the cost of systems may give us some help in pushing developers to write better code from the beginning, learn to use efficient patterns and avoid anti-patterns, and perhaps even get more time to tune systems. However, those are skills that many of us need to improve, learning how to find code that can be improved, and what techniques to use to do so. We have lots of articles that help, as to Brent Ozar, Erik Darling, sqlSkills and others. There are lots of ways to improve your skills, and they can help improve your bottom line. If you work on them.

    Steve Jones

    Listen to the podcast at Libsyn, Stitcher or iTunes.