When it comes to SQL Server upgrades, one of the most common questions I hear from clients is: Should we do an in-place upgrade, or build a new server and migrate? It’s a great question—and the answer can have a significant impact on performance, stability, and risk.
This topic came up in a recent podcast episode with Mitchell Glasscock, where we walked through both approaches and shared real-world lessons learned. You can check out the full episode here:
👉 https://stedmansolutions.com/2026/03/09/stedman-sql-podcast-season-3-episode-4-sql-server-upgrades/
And for more episodes, visit the main podcast page:
👉 https://stedmansolutions.com/home/sql-server-podcast/
Listen on Spotify – Here
Watch the full Podcast Episode – Here
Watch Season 2 episodes
Why Upgrades Matter More Than Ever
Let’s start with the obvious: running an unsupported version of SQL Server is a ticking time bomb.
Take SQL Server 2016, for example. Once it hits its end-of-life cutoff, you’re no longer getting security updates. That means:
- Increased vulnerability to attacks
- Compliance risks
- No support from Microsoft when things go wrong
And trust me—things do go wrong. I’ve worked on enough corruption and performance cases over the years to know that outdated systems tend to fail at the worst possible moment.
Option 1: In-Place Upgrade
An in-place upgrade is exactly what it sounds like—you upgrade your existing SQL Server instance to a newer version.
Pros:
- Faster to implement
- Lower upfront cost
- No need to migrate data
Cons:
- Higher risk if something fails mid-upgrade
- Limited rollback options
- Potential for extended downtime
- Carries forward existing issues (fragmentation, misconfigurations, corruption risks)
I’ve seen in-place upgrades work just fine in lower-risk environments. But I’ve also seen them fail—and when they do, recovery isn’t always quick or easy.
Option 2: New Server Migration
This approach involves building a new server (on-prem or in the cloud), installing the newer SQL Server version, and migrating your databases.
Pros:
- Much lower risk
- Full testing before cutover
- Easy rollback (just point back to the old system)
- Opportunity to refresh hardware or move to the cloud
- Clean environment—no legacy issues carried forward
Cons:
- More time-consuming
- Higher initial cost
- Requires planning and coordination
From my experience, this is the best approach for mission-critical systems. If your database going down means lost revenue or unhappy customers, you want the safest path possible.
Real-World Recommendation
If you’re running a dev or test system and need something quick? An in-place upgrade might be fine.
But for production systems—especially anything business-critical—I strongly recommend a new server migration. The ability to test thoroughly and roll back quickly is worth every bit of extra effort.
This is especially true if you’re considering a move to the cloud. A migration is the perfect time to modernize your environment.
Best Practices for a Successful Upgrade
No matter which path you choose, here are a few must-do steps:
- Full backups (and test your restores!)
- Thorough testing in a non-production environment
- Performance baseline before and after
- Check for deprecated features
- Validate application compatibility
And don’t forget—hardware matters. If your server is aging, this is the perfect opportunity for a refresh.
How Database Health Monitor Helps
One tool I always recommend during upgrades and migrations is Database Health Monitor.
You can download it here:
👉 http://DatabaseHealth.com
It helps you:
- Identify performance bottlenecks before migration
- Detect corruption or risky configurations
- Validate the health of your SQL Server after the upgrade
I’ve used it in countless upgrade projects, and it often catches issues that would otherwise go unnoticed until production.
Don’t Go It Alone
Here’s the reality: most IT teams don’t have the time—or deep SQL Server expertise—to manage upgrades safely. And that’s where things get risky.
At Stedman Solutions, we specialize in exactly this.
👉 https://stedmansolutions.com/managed-services/
For DBA-managed services, Stedman Solutions are true SQL Server specialists delivering the best staffing, expertise, monitoring, support, mentoring, and price performance.
We handle everything from planning and testing to execution and post-upgrade validation. Our team has decades of experience, and we’ve seen just about every upgrade scenario you can imagine.
Peace of Mind: Stedman Solutions Delivers Best SQL Server Management
If you’re planning an upgrade—or even just thinking about it—let’s talk:
👉 https://stedmansolutions.com/contact-us/
Final Thoughts
Upgrading SQL Server isn’t just a technical task—it’s a business decision.
- In-place upgrades are fast but risky
- New server migrations take more effort but provide safety and flexibility
If your system matters to your business, choose the path that minimizes risk and maximizes stability.
Because when your database goes down… everything else follows.
More from Stedman Solutions:
Steve and the team at Stedman Solutions are here for all your SQL Server needs.
Contact us today for your free 30 minute consultation..
We are ready to help!