SSMS version upgrade

Question

Hi All, we are changing SSMS version in live system from 2012 to 2022, there are few jobs already running in our system on daily basis, could you please help me out for the steps we need to take.

Answer 1

Hi

Kindly ensure these steps carefully

SSMS Independence:

SSMS is a client tool and does not directly affect the SQL Server engine or the jobs running on the server.

However, ensure compatibility of SSMS 2022 with your SQL Server versions. SSMS 2022 supports SQL Server versions from 2012 onwards. Backup

Configurations:

Document and back up the current SSMS configurations (e.g., registered servers, connection details, etc.).

Take a full backup of the SQL Server environment, including system databases (master, msdb, and model).

Check SQL Server Jobs:

Review the jobs running in the system to identify any dependencies on scripts, tools, or features specific to SSMS 2012. Ensure jobs are tied to the SQL Server Agent, which is independent of SSMS.

Test Environment Setup:

Set up a test environment that mirrors the production setup to validate the SSMS upgrade before applying it to the live system.

Regards

Vignesh K

Answer 2

SSMS version ... help me out for the steps we need to take.

None, SSMS is just a tool sending plain T-SQL commands to SQL Server engine.

Answer 3

Hi Manjunath Aralikatti,

SSMS is a tool to manage SQL infrastructure, it will not affect jobs when you upgrade it.

Regards，

Zoe Hui

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Answer 4

There are two ways to run the upgrade: in-place and move to new hardware. Since you are moving from SQL 2012 to SQL 2022, in-place upgrade can be difficult. It is not that SQL Server does not support it, but I don't think there is any version of Windows Server that supports both.

If you nevertheless do an in-place upgrade, the jobs are not an issue, they will keep moving along. If you move to new hardware, you can easily script them from SSMS and then use that script on SQL 2022.

No matter which path you take, I advice that once you have performed the upgrade, you enable Query Store on the database. Keep the database in compatibility mode 110 for a week or two. Then you can flip the switch to 160 to get access to the most recent optimizer improvements. Unfortunately, while they are improvements, they can back-fire and one or two queries may start to perform badly. With help of Query Store you can quick resolve the urgent situation by forcing the old plan, and then you can investigate the case for a more long-term solution later on.