I had a great opportunity to present two sessions at #SQLSatJax (SQL Saturday Jacksonville for those who don’t hashtag) on Saturday, May 14. Both of my sessions talked about high availability as it relates to both on-premises SQL Server and all varieties of Azure SQL. Jeff Taylor (t) and his team did a fantastic job and it was wonderful to be at an event with so many familiar faces but, even better, many new ones! I enjoyed both of my sessions, received some complimentary and constructive feedback, and learned things from the hallway/outdoor courtyard conversations as well.
In fact, it is conversations like those at past events that led me to put a slight twist in at the end of both of my sessions. Make no mistake, both of these sessions (“HA/DR Fails and Fun: I Broke It So You Don’t Have To” and “This Is Fine: Firefighting for the DBA”) are technical. Topics covered run the gamut from Always On Availability Groups to replication, from fault domains in Azure to other gaps in the cloud’s “magic” and how to fill those to keep your data and applications highly available. We delved into rev.io‘s cloud migration journey and how making the decision to migrate to the cloud (as we have) can play into the evolving high availability and disaster recovery needs of an organization.
The twist I added, though, was some slides and discussion at the end of each session about the mental toll that being on-call and responsible for highly available environments can take on the individuals and teams involved in supporting them. I speak from personal experience here. I have triggered personal medical issues because of this. I have left jobs because of this. I have made mistakes that could have cost a company money had our customer decided to punish us (thankfully, they did not).
As I was preparing these sessions in late 2021, it occurred to me that, in all of the Azure SQL/SQL Server high availability sessions I have presented over the years, it never occurred to me to counsel people about the personal toll that it can take. I am glad I started doing this in Jacksonville and look forward to presenting these sessions at other events. They triggered some wonderful post-session discussions about ways to deal with the stress of positions like this and I look forward to having those in-person and virtually as the year goes on.
I write this sitting at the airport waiting to leave on a much-needed vacation. I’m grateful to work at an organization like rev.io with leaders in technology who understand that people need to rest and recharge and I look forward to doing just that. If you find that your current role (and the technical leadership there) isn’t prioritizing your wellbeing, my DMs are open @sqlatspeed or you can email me at firstname.lastname@example.org. I’m happy to chat about some tips and tricks that have helped me through the years or make connections via #sqlfamily to help find you a new opportunity. Be well – remember that you are not highly available even if you think you are.