Author: way0utwest

  • Being Reasonable

    The last two years have changed the way many of us work in technology. The pandemic allowed many of us to work remotely, a challenge that many companies are struggling with. Or perhaps, management is struggling with and employees appreciate. In any case, no matter what your situation, the way we work has changed.

    The change wasn’t easy at times, and even though many people appreciated the extra time in their day from not commuting to work, they often had other challenges. Co-existing with others in a residence, finding a place to work that allows concentration, and even learning how to separate work from home life. These have been issues for many data professionals and other technologists. Even if we’ve had an easy time adapting, not all of our colleagues have felt the same way.

    One of the core values that we have at Redgate Software is being reasonable. It’s a somewhat amorphous value that I didn’t know how to interpret or act on at first. Our former CEO repeated this often in updates, to the point where I have heard other management and employees use the verbiage in meetings on a regular basis.

    I think as a company, we’ve learned how to be reasonable with others. We don’t overly rely on policies or rules to guide us in how we accomplish work and interact with each other. Instead, we use judgment, and managers are flexible in their interactions with employees. As a Type-A, driven American, it has sometimes felt strange to not have everyone trying to outwork everyone else. It was an adjustment for me.

    The idea is not that we do little work or avoid work, but that we avoid working too much. It’s not about the hours anyone puts in, it’s the contribution they make to their department. No one watches the parking lot to see who’s in the office or who’s logged in. Instead, we expect people to manage themselves, meet their commitments, and be accountable for the tasks they’ve been assigned. At the same time, we cover for each other and support the team. We’ve had people out sick, out for maternity/paternity leave, or struggle with other life-altering issues. The rest of their team will help cover for someone, knowing they will do the same for us.

    We treat each other as humans, have empathy for others, and act towards others as we would want to be treated. At the same time, we have goals and missions to drive us forward to build a better company. We find balance in how we do this, and it’s worked very well for over 20 years. In many ways, it’s how I try to live life. There are good and bad days. There are busy ones, some hectic, chaotic times, but also slower times when I can recover and recharge.

    It is really hard to describe what being reasonable means, and at times I am not quite sure how to act in a situation, but I try to put myself in someone else’s shoes, see their point of view, and then decide how I would want to be treated. That usually guides me as to how I should proceed. It’s worked well for 15 years for me and I look forward to being reasonable for the next 15.

    Steve Jones

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

  • Daily Coping 29 Jul 2022

    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 identify what helped you get through a tough time in your life.

    I’ve mostly had a good life, but there were definitely some tough times. However, what has helped me, or what I did to cope changed over time.

    Earlier as an adult, I had financial struggles at times. I used stubbornness and persistence to make my way through things. I took two or three jobs to make ends meet and overworked myself. I know I’ve had more than my share of 100+hour weeks.

    When I was struggling early in my first marriage, I went to counseling with my wife. I leaned on a therapist, first together, then on my own to help me come to terms with the need for a divorce.

    When COVID hit, I found myself in a strange place. A telecommuter of 20 years that wasn’t used to being at home for months at a time. I leaned on my wife and kids to distract myself from the sameness. I also focused on cooking more food for the family, which was good. Unfortunately, I also drank too much alcohol while cooking. Luckily, I’ve gotten better and less drinking and healthier food as the pandemic stretched on.

    Coping can change over time. What worked at one point in my life, might not work later, or might not be appropriate. I have tried to approach things this way, changing when needed: “strong opinions, loosely held.” When I need to change, I will.

  • Daily Coping 28 Jul 2022

    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 if you can’t change it, change the way you think about it.

    I’ve been working on growing SQL Saturday back to a series of events that make the world better for data professionals. My business partners and I started this idea, grew it, and gave it to the PASS organization. When they failed, I got the new owners to donate it back to the community and it runs as a 501.c.3 US chartable foundation.

    At the beginning of 2022, I was hoping for 10 events. Early in the year, I wasn’t confident about this. As of a couple months ago, I was confident in 10 and possibly more. Now, we’ve got 8 on the schedule and 4 completed. A couple more might come about.

    There are two things happening now that I can’t change. One is that a few people are upset about SQL Saturday, mostly because of the mismanagement by the PASS organization. I’m working to change minds, but I also know I can’t get upset by their emotions and feelings. All I can do is show that I run the franchise differently and hopefully get them to realize that.

    The second thing is that a few people are still nervous about events. That is understandable, and I have worked to remember that my view of the world isn’t more or less valid than theirs, and I need to work with them. I have learned to accept their decision not to run events if they are concerned.

  • The Azure Carrot

    Microsoft wants more people to move their database workloads to Azure. They are constantly adding new features, capabilities, even tools to help people move databases to some part of Azure. It’s working well, as the latest quarterly report shows tremendous growth in Azure revenue. We don’t know precisely how SQL Server or Azure SQL databases impact this, but I certainly see more and more customers moving relational workloads to the cloud. Some to Azure, some to other providers.

    In an effort to entice people, Microsoft has a promotion that they were running in March, which was asking SQL Server 2012 customers to move to Azure and save with free extended security updates. They reiterated the promotion on July 12, when SQL Server 2012 went out of support. They calculate savings and promote benefits, which might be tangible and desirable to some of you. After all, not having a supported platform isn’t an option for some people.

    I don’t know how I feel about this. While we recently had a security update for SQL Server 2012, I know that it’s an older platform and at this point, it’s 10 years past RTM. It is probably time to upgrade to a newer version, which should be 2019 if you can’t wait and SQL Server 2022 if you can wait until the end of the year. I can’t imagine that your workload from 2012 won’t run on 2019, but it’s possible there are some issues.

    I’ve run older versions of SQL Server that weren’t supported and often didn’t worry. I knew what worked and what didn’t, and after a few years, it was unlikely that anything in the product would break. However, that was in an environment that was not regulated or certified, which wasn’t always the case. I have worked in places where we would upgrade whenever we got to the end of mainstream support as we weren’t interested in paying for extended support.

    I also think that while SQL Server is very mature, and it’s possible that you don’t need new features, you do want a platform that is secure. That means you do want support and fast action if an exploit becomes published. There is also the case that we often want developers working on modern platforms, both because they can take advantage of better language constructs, but also because this helps retention. Try hiring for an all SQL Server 2012 environment v a SQL Server 2019 one. You might find people, but a lot of the talented ones would prefer to work on a modern platform, not a decade old one.

    If you are running SQL Server 2012 (or 2008x) and considering the cloud, check out the promotion. It might help you make a decision on whether to upgrade locally or move to Azure.

    Steve Jones

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