Over the past several weeks, many of you have probably noticed subtle hints throughout my blog. A few references to new technologies. A growing interest in AWS and PostgreSQL. Discussions around new automation ideas. Even a few comments about learning new systems.
If you picked up on those clues, you were right.
Today, I’m excited to officially share that I’ve joined ESO as a Senior Database Administrator.
Changing employers is certainly news, but that’s not really what this post is about.
This post is about growth.
It’s about continuing to challenge myself as a database professional and embracing opportunities to learn, build, and solve new problems.
Most importantly, it’s about sharing that journey with all of you.
One of the most common questions I receive from other IT professionals is:
“How do you know when it’s time for a career change?”
There isn’t a simple answer.
Sometimes the answer is obvious.
Other times, you’re fortunate enough to be in a role where you’re still learning, surrounded by talented people, and contributing to meaningful work.
That was certainly my experience at Dayforce.
The challenge wasn’t finding something better.
The challenge was recognizing an opportunity that aligned even more closely with where I wanted to grow as an engineer.
I wanted to share why I made this transition, what excites me about this next chapter, and how it will shape the technical content you’ll continue to see here on my blog.
While my employer may have changed, my passion for database administration, automation, and solving real-world problems has not.
If anything, it’s only getting stronger.
Every position I’ve held has contributed to the DBA I am today.
Some roles taught me how to troubleshoot under pressure.
Others taught me how important communication is during a production incident.
Some reinforced the value of automation, while others reminded me that consistency and documentation are often just as valuable as technical skill.
My time at Dayforce was no exception.
Working in a large-scale SaaS environment allowed me to support enterprise SQL Server environments, strengthen my automation skills, and experience firsthand the operational discipline required to manage databases at scale.
More importantly, I had the opportunity to work alongside talented professionals who challenged me to become a better engineer.
For that, I will always be grateful.
One of the reasons I’ve stayed passionate about database administration for so many years is because the technology never stops evolving.
When I began my career, success meant keeping SQL Server online.
Today, success means understanding an entire ecosystem.
Modern database professionals are expected to understand far more than just SQL Server.
We work with cloud platforms.
We automate repetitive work.
We monitor distributed systems.
We think about resiliency, observability, security, and performance as a complete solution rather than individual tasks.
That’s exactly the type of work I enjoy.
The opportunity at ESO allows me to continue expanding my knowledge while contributing to technologies that include:
- SQL Server
- PostgreSQL
- AWS
- Automation
- Monitoring
- High Availability
- Platform modernization
- Operational excellence
For someone who genuinely enjoys learning, that’s an exciting place to be.
Starting a new position always comes with a learning curve.
New people.
New environments.
New tools.
New challenges.
While that can feel intimidating, it’s also one of the most rewarding parts of our profession.
Every new environment teaches us something.
More importantly, every new challenge expands our perspective.
Ultimately, every problem we solve makes us a little better than we were yesterday.
That’s one of the reasons I continue writing this blog.
Teaching others has always been one of the best ways for me to reinforce my own learning.
If you’ve been following this blog, not much is changing.
You’ll continue to find practical, real-world technical content focused on solving problems that database professionals encounter every day.
Topics you’ll continue to see include:
- SQL Server Administration
- High Availability
- Performance Tuning
- Backup and Recovery
- PowerShell Automation
- Azure SQL
- PostgreSQL
- AWS Database Services
- Monitoring
- Disaster Recovery
- Operational Best Practices
As I gain experience with new technologies, I’ll continue sharing lessons learned, scripts, troubleshooting techniques, and practical solutions that you can apply in your own environments.
Throughout my career, my goal has always been simple:
Share knowledge that makes another DBA’s job a little easier.
That mission isn’t changing.
It’s expanding.
Looking back on this transition, a few lessons stand out.
- Career growth isn’t always about leaving something behind. Sometimes it’s about moving toward a new opportunity.
- The best engineers never stop learning.
- Technology changes constantly, but curiosity remains one of the most valuable skills you can develop.
- Every new environment offers an opportunity to improve both technically and professionally.
- Sharing what we learn benefits the entire community.
If you’re reading this as another database professional, here’s my challenge to you.
Take a few minutes this week to think about your own career.
Ask yourself:
- What technology have I been putting off learning?
- What skill would make me a better engineer a year from now?
- What project could push me outside my comfort zone?
Then take the first step.
Read the documentation.
Build a lab.
Write a PowerShell script.
Deploy a new service.
Learn PostgreSQL.
Experiment with AWS.
Growth rarely happens by accident.
It usually starts with curiosity and a willingness to try something new.
One of the reasons I started this blog was to document what I was learning and, hopefully, make another DBA’s job a little easier.
That won’t change.
If anything, this new chapter gives me even more opportunities to explore new technologies, solve new problems, and share those experiences with all of you.
To my colleagues at Dayforce, thank you for the opportunity to learn, grow, and work alongside such talented people. I sincerely appreciate everything I gained during my time there.
To my new teammates at ESO, thank you for the warm welcome. I’m excited to contribute, continue learning, and help build great things together.
And to everyone who has taken the time to read, comment, or share one of my articles over the years, thank you for following along.
Here’s to the next chapter.
I can’t wait to see where this journey takes us.
Every new chapter starts with curiosity, a fresh notebook, and a willingness to learn. Looking forward to what comes next.
The post A New Chapter: Why I Made the Move from Dayforce to ESO appeared first on GarryBargsley.com.
