Looking Back at 2016, Looking Ahead to 2017
This post was supposed to happen in January. It was going to be “Oh, hey, it’s a New Year and blah, blah…” — we saw what happened to that. Better late than never. I’m going to cover where 2016 went, what I want to do differently in 2017, my recent ITIL training, and a few other goals.
In 2016
My career goals for 2016 were straightforward — just work on becoming a better SQL DBA. I focused on the fundamentals; I spent a significant amount of time working with Availability Groups and got some time helping refine our production monitoring. I built some SQL scripts to automate parts of the build process. Throughout all of it, I kept learning through PASS virtual chapters, Ozar’s daily emails, a Safari Books subscription, and whatever else I could find. One lesson learned: you can hit information overload quickly if you’re not careful.
I’ve also realized I gravitate toward certain topics more than others. Performance tuning, SQL development, and automation genuinely interest me in a way that routine backups, restores, and general administration don’t — probably because I’ve spent so many years on the general admin side. The routine work is still important; it just doesn’t excite me the way it used to.
In 2017
The big focus for 2017 is development. I want to bring my SQL dev skills above average and get more serious about PowerShell and Python. Longer term, I’m interested in moving further into the development side of the DBA role.
I’ve also been working on understanding the business side of things, including management. Do I want to be a manager? Not particularly — but I want the option, and I think leadership skills make you a better DBA regardless of title. That’s part of why I jumped at a three-day ITIL course this year. The certification was a bonus; the real value was understanding where management thinking is headed.
Other Goals
I want to participate more in the SQL community — Twitter, #tsql2sdays, blog posts, and at least one more SQL Saturday. When I was in Tulsa, I was a regular at the local SQL User Group and learned a lot from those sessions. I’m hoping to make it to a few meetings here in Denver when the topic lines up.
I’d also love to make it to PASS Summit one of these years, cost permitting. And somewhere down the line, Ozar’s Senior DBA class is on the list.
On certifications: I’ve considered pursuing my MCSE. Will it move my career significantly? Probably not. But I’m coming around to the idea that if you’re passionate about what you do and want to demonstrate commitment, why not? I’ve long believed that as IT matures, certifications will matter more — not as gatekeepers, but as signals of seriousness. Others will disagree, and that’s fine.
Key Takeaways
- Specialization is natural — lean into the areas that genuinely interest you rather than spreading yourself thin.
- Leadership and business awareness are worth developing even if you never want to manage people.
- Community involvement compounds over time — user groups, blog posts, and SQL Saturdays all pay back more than they cost.
- Information overload is a real risk; be deliberate about what you consume and what you actually apply.