Brent Ozar had a post SQL Server 2016 and the Internet: Forced Updates, Phoning Home. "Issue #1" is ‘You probably shouldn’t run 2016 side-by-side with older versions.’ So, I checked the language in all the SQL Server install ULAs and they all say the same thing. I know some shared components will be upgraded to the newest version on a server upon install of said version and feature, but this has been around for many Glenn Berry guided instance installs. Is there something I’m missing?
SQL Server 2016 – Running Side-by-Side with Older Versions
sql serversql-server-2016
Related Question
- SQL Server 2016 – Running Side by Side with Previous Versions
- Sql-server – Removing older components after upgrading
- Sql-server – SQL Server Data Tools for VS 2015 – Anyone using for SSIS development to multiple versions
- Sql-server – SSIS Not Executing any Script Task
- SQL Server Management Studio 2017 – New Explain Feature Overview
- Sql-server – sp_databaserestore: “stopat” gives error “no database backup found”
- SQL Server 2016 – Configure Linked Server to Oracle 12c
- SQL Server 2016 Install Error 2337 – Could Not Close File
Best Answer
It's important to read the reasons pertaining to this freighting revelation
The way I read that, the concern is the potential for one version to overwrite at a later point in time the files shared and needed by another version. This is probably a result of DLL Hell. You can see this on the Wikipage,
In light of that, the suggestion not to run two versions side-by-side makes perfect sense.
Future Safeing the Problem
One way to avoid DLL hell, is to upgrade and install Ubuntu which doesn't have such a problem. SQL Server 2017 will run on Ubuntu. This means that SQL Server 2018 will likely also run on Ubuntu. At such time, you'll be able to run both versions concurrently. So it's nice to see the Linux work paving the way forward. For Linux, SQL Server is currently self-contained in the
/opt
directory, and packaged officially withdpkg
(which supports multiple versions).