What the Heck is Happening?
I think we’re seeing more and more DBAs working in environments where there isn’t just one database engine anymore. SQL Server might still be everywhere, but now there’s Postgres, MySQL, cloud-managed databases, and whatever else the application team decided they needed. Companies are either shifting database engines entirely or running mixed environments with multiple flavors. There’s a lot of noise out there, and most of it feels like an emotional reaction more than a technical one. Will SQL Server die off? Is my skillset obsolete? In my opinion: it depends (if you’re a DBA reading this, you should appreciate that answer). The field evolves too rapidly to stay stagnant, and I think that knowing another database engine is essential for any data professional.
Why Now?
The demand for learning another database engine is drastically increasing. I’m a MS SQL Server DBA through and through, and I’ll never stop working with it as long as I’m able to. But I’m learning PostgreSQL now, before I’m asked to. If I wait until my boss says “we have an initiative to move workloads to Postgres,” it’s already too late. The time to learn isn’t when you’re forced to start owning it. I don’t want to be learning Postgres on the fly while I’m touching production systems.
The Mental Approach
I’m not gonna lie, it’s overwhelming to feel like I’m starting from zero again, but small achievable goals move the needle regardless. So I’m taking the same approach I took with SQL Server: learn something, break something, figure out why I broke it, and then write about it.
What I’m Excited For
I’m very excited to start working more in-depth with a new database engine as well as learning how Linux works along the way. I’m especially interested in seeing how Postgres behaves at scale and what the enterprise side of the ecosystem looks like, including Azure Database for PostgreSQL, and I can’t wait to share what I learn.
Resources
If you’re taking on the challenge to learn Postgres like me, the biggest resource is your network. Reach out, ask questions. Beyond that, here’s what I’m reading:
- How Linux Works, 3rd Edition: What Every Superuser Should Know: Great book to understand how Linux works since most Postgres deployments sit on top of Linux.
- Introduction to PostgreSQL for the data professional: Amazing introductory book that compares SQL Server and Postgres. Gives you tons of background and useful actionable skills to get you rolling.
- PostgreSQL 16 Administration Cookbook: Solve real-world Database Administration challenges with 180+ practical recipes and best practices: Great reference guide for “how to do this and why to do it”.
- Mastering PostgreSQL 17: Elevate your database skills with advanced deployment, optimization, and security strategies: Good for when you get further into Postgres and will help you take your skillset to the next level.
- Brent Ozar’s Smart Postgres: If you’re familiar with any of Brent’s SQL Server related performance training, no explanation is needed here. Several useful offerings in the Postgres space.
I’ve also spun up a Hyper-V VM running Ubuntu Server with Postgres installed to apply what I’m reading. And I’d recommend connecting with these folks on LinkedIn if you’re getting started:
You can even reach out to me if you’d like and I’d be more than happy to help answer any questions or direct you / connect you to a resource in my network.
Wrapping Up
Honestly, im finding out how overwhelming it is to look at an entirely new database ecosystem and not even know where to start. If writing about the things I’m learning helps someone else get started a little faster, then it’s worth it. Reach out, ask questions, and share with the community. I’ll be continuing to blog about things I’ve learned and my journey to get up to snuff on Postgres and I’m excited to share with you all what I find along the way.
DBA Unfiltered 
Leave a comment