Should I Upgrade Now? Or Wait for SQL Server 2019?
“Should I install SQL Server 2017 now? Or wait until SQL Server 2019?”
One of our Remote DBA clients recently asked me that question. They have a set of aging SQL Server 2008 R2 instances used for production, test, and development. SQL Server 2008 and 2008 R2 Extended Support ends July 9, 2019, and the company wants to upgrade those instances before time runs out. SQL Server 2019 is currently in a preview state; the official release date hasn’t been announced.
So here’s their quandary
- Research. What applications will be affected? Do those applications need to be certified/supported by a vendor on the newer version of SQL Server? Will your internal development teams be able to sign-off on the upgrade? Are there other dependencies that must be considered? Are there other projects that will compete for key resources.
- Plan. The order in which the SQL Server instances are upgraded must be planned and sequenced in a way that is efficient while minimizing risk. Backups must be verified, rollback plans must be documented, and schedules must be coordinated.
- Test. Before upgrading the SQL Server instances, testing should be conducted to ensure that the upgrade plans will work and that the applications will continue to function.
- Upgrade. Once you’ve researched, planned, and tested the upgrade and process, you must actually schedule and perform the upgrade. Users must be notified.
These items take time to coordinate and perform. So, it would be good to start the upgrade process as soon as possible. This means not waiting for SQL Server 2019, but going with a SQL Server 2017 upgrade.
On the other hand, since upgrading is a time-consuming and costly experience, it makes sense to future-proof the investment by upgrading to the latest version, if possible. You can plan the upgrade while waiting for the official bits to be released to manufacturing. Once SQL Server 2019 is released, you can kick the project into high gear and proceed with the testing and rollout. At the end of the upgrade, you’ll have the newest version in place. There’s no point in doing this twice if they can avoid it.
That is the dilemma.
But before we make a decision, we should consider some other questions.
- How many SQL Server instances must be upgraded?
- How long will it take to upgrade the instances?
- How much testing must be done before upgrading?
- How long will the new hardware and/or virtual machines take to requisition?
- Are there compelling reasons or features in the newest version that would influence your decision? (See this Microsoft Technical White Paper for SQL Server 2019)
- Are the database servers so critical that being on the “bleeding edge” is undesirable? Would it be better to wait for a CU or two before installing?
- What are the implications of missing the Extended Support deadline? (Assuming you’re upgrading from SQL Server 2008 or SQL Server 2008 R2. If you are upgrading from a newer version, the Extended Support deadline is not as pressing. See this support document for a description of different support levels.)
So, what to do? Upgrade to a newer version now and go through the process again sooner rather than later? Or wait an indefinite amount of time in hopes that SQL Server 2019 will be released in time for you to upgrade before July 9, 2019?
We’re seeing a lot of IT shops wrestling with this dilemma. So, if this is you, you’re not alone. Keep in mind that not upgrading comes with some significant risks so you will probably want to take that option off the table.
Clearly, there is no one-size-fits-all answer to the question. As with many technical questions, the best answer is: It depends. It depends on your priorities, your budget, your tolerance for risk, and your other activities.
Upgrading to the goodness of a newer version will be beneficial in the long run. Just make sure you take the time to do it right. Have some questions? Leave a comment. Or if you’d rather have a more detailed discussion, feel free to reach out to us by phone (888.412.7376) or by email at info@theserogroup.com.
2 Responses
Plan to upgrade to SQL Server 2017, but don’t pull the trigger until 2019 is released so you can buy that version on a volume license with downgrade rights to your tested 2017 installation.
This.