Voice of the DBA

Category: Editorial

  • Burning Out

    We tend to work a lot of hours as data professionals, developers, even IT management. It seems that we often are in the office at night, on weekends, and anytime there is a crisis. Even when we don’t have down systems, it seems the pressure to continue to build new features, functions, and ensure systems are operating well leads many of us to work longer hours than the expected 40 hour week. In fact, there are no shortage of companies that expect IT employees to work more than 40 hours every week.

    This isn’t limited to IT. Doctors, lawyers, and plenty of other professions put in extra hours at work. Even teachers often do work at home. I’ve seen this first hand this past year with my oldest son teaching 5th grade. He spends a fair amount of time doing work at the kitchen counter, not unlike what I used to do when I worked as a DBA in a few companies.

    I have an amazing job. Along with Grant, Kathi, and Kendra, we all have good positions. We work for an amazing employer, Redgate Software, and we get to travel around, speaking at various events and meeting lots of you in the SQL Server community. We also all work from home, which is becoming more common, but it still a luxury for many. In the era of double, or triple, digits of minutes to commute to an office, that’s a blessing.

    Recently, I saw this note from Kendra, and I get it. I’ve been there and I have a tendency to work too much. I like my job, and I’ve enjoyed both being a DBA and Developer, as well as running SQLServerCentral. I enjoyed it so much that there were a number of years where I struggled to take much vacation, much to the dismay of my wife. Even while on vacation, I’d be checking email and the status of the site. Early on, I was afraid to take any time away from this site, scheduling time to log on, answer a few questions, write an editorial, and even edit a submission on weekends and during vacations.

    I got better over time, balancing out work, though a few years ago, I was where Kendra is now. I had made too many commitments and really, too much travel.  I’ve felt what Andy described here, feeling tired and short tempered. I re-read some of my own thoughts and eventually talked with my manager. I scaled back travel, found a new hobby coaching, and I’ve felt much more balanced across the last year. Life is still chaotic, but it’s a variety of things I enjoy. Plus, I still have trouble sitting still for more than a few days.

    Working hard feels good. There’s a sense of accomplishment from completing tasks and solving problems. Many of us enjoy this, but it’s easy to become unbalanced with work and life. It’s also easy to allow your boss to overwork you when we feel pressure to stay employed. Those are hard situations in which to find yourself, and I can only advise you that you can push back to find some balance. Most bosses, even bad ones, don’t want to fire people. It’s disruptive, expensive, and makes a bad situation even worse.

    Remember, we work to live, not the other way around. Keep that advise close by in times of stress and learn to take time off, enjoy time with friends and families, and ensure you have something outside of work in which you can sink some passionate time.

    Steve Jones

    Listen to the podcast at Libsyn.

  • Republish: Small Experiments in Data

    It’s time for another SQL in the City Summit. In Austin this time. You get a republish of Small Experiments in Data

  • Republish: No State Based Deployments

    Traveling to SQL in the City Austin today, and it’s a busy day. Getting ready for this event and then 3 more on the other side of the world. A republish today: No State Based Deployments.

  • What Limits Do You Want in 2019?

    SQL Server 2019 is in development, and likely getting close to being released. I mean, it is named 2019, so I assume we’re down less than 6 months of time before we start deploying it. One of the decisions that Microsoft will need to make before release is what the costs for each edition will be, as well as the hardware limits involved. I assume other items like OS support and feature mix will also be decided, but those are less important to me after SQL Server 2016 SP1. Most features just work on all editions.

    Recently Glenn Berry proposed some new limits. He requests that 2019 Standard edition raise it’s core limit to 64 and the RAM limit to 256GB. These would be raises from 2016, where we were limited to the lessor of 24 cores or 4 sockets and 128GB of RAM. We do get 32GB of RAM for In-Memory objects and 32GB for columnstore as well. There were no changes for SQL Server 2017.

    What do you think? Are these limits that make sense in a world where hardware advances and a “small” system is much larger than anything we used at the turn of the millennium? Since data sizes continue to grow and most of us want (and need) more hardware, is 128GB of RAM crippling to a small database server? Do you think that more cores are needed to run a Standard Edition server?

    I might also point out that raising limits might keep some people on Standard Edition, but it might also get more people to move from SQL Server 2008 to SQL Server 2019, Standard to Standard. At lower limits, when you might be limited to processor and not core licensing, why not stay on 2008 if you can’t get a much faster system?

    Personally, I think that Microsoft ought to raise limits somewhat. I do think 256GB of RAM makes sense, even if that includes the In-Memory and Columnstore usage. For cores, 24 to 64 seems like a lot, but what about 40 cores? Who cares on sockets, let’s make this simple. Cores. These days, no one is going to get 8 sockets at 4 cores each, but if they do, what does it matter? Let them use all of them on Standard Edition.

    Steve Jones

    Listen to the podcast at Libsyn