![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 84%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKS%3C/text%3E%3C/svg%3E)
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
3,064 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Two options:
- You make an in-place upgrade. You simply download the iso, start Setup and select the Upgrade alternative. See image below.
- You create a new VM with SQL 2022 and move all the databases with BACKUP/RESTORE.
The advantage with the latter is that you can keep the old version as a reference if there is a performance regression, or there are some other issue. On the other hand, the first option is simpler, not the least given the number of databases. If you go for an in-place upgrade, make sure that you have a snapshot or similar of the VM that you can revert to, in case there is an unexpected error.
I'm assuming here that you have an OS that SQL 2022 supports. Windows Server 2019 should be OK. I am not sure about Windows Server 2016.