<div>
In place upgrades of critical servers just never seem to work perfectly again... Just like an airplane crash, sometimes you get lucky, but not often...
</div>


In place upgrades of critical servers just never seem to work perfectly again... Just like an airplane crash, sometimes you get lucky, but not often...

Infrastructure Manager

Matthew McGlone

<div>
What's the frontend that SQL is serving? Is it compatible with the updated database version?<br><br>Go with Server 2019 if you can and a newer version of SQL.<br><br>If stuck on 2016 for both, then make sure both are up to date before restoring the .BAK file (backup) into the new SQL. It will update the existing database and stamp it with the new version.<br><br>Keep this in mind as that means no going back.<br><br>And, of course, make sure to back everything up before, during, and after. :)
</div>


What's the frontend that SQL is serving? Is it compatible with the updated database version?

Go with Server 2019 if you can and a newer version of SQL.

If stuck on 2016 for both, then make sure both are up to date before restoring the .BAK file (backup) into the new SQL. It will update the existing database and stamp it with the new version.

Keep this in mind as that means no going back.

And, of course, make sure to back everything up before, during, and after. :)

<div>
I would build new VMs with the later version of Windows, load the later version of SQL, and then backup/restore the SQL data and point things over to the new server. That's the easiest way that gives you a way to go back in case something goes wrong.
</div>


I would build new VMs with the later version of Windows, load the later version of SQL, and then backup/restore the SQL data and point things over to the new server. That's the easiest way that gives you a way to go back in case something goes wrong.

<div>
<div class="content wysiwyg-content fr-view">
I currently have several Windows 2008 R2 servers running SQL Server 2008. &nbsp;i need to upgrade both. I was hoping to upgrade Windows to 2016 and SQL Server 2016. &nbsp;But I'm not sure if I should do it side by side - building a Windows Server 2016 VM and installing SQL Server 2016 - then restoring a backed up database on the new server. &nbsp;<br><br>Or the second option of doing an in-place upgrade to Windows Server 2016 and SQL Server 2016. &nbsp;It should be noted that these are production servers.<br><br>Any recommendations?<br><br>
</div>
</div>



I currently have several Windows 2008 R2 servers running SQL Server 2008.  i need to upgrade both. I was hoping to upgrade Windows to 2016 and SQL Server 2016.  But I'm not sure if I should do it side by side - building a Windows Server 2016 VM and installing SQL Server 2016 - then restoring a backed up database on the new server.  
Or the second option of doing an in-place upgrade to Windows Server 2016 and SQL Server 2016.  It should be noted that these are production servers.
Any recommendations?

Recommendation for upgrade path to Windows Server and SQL Server

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.