Skip to content

upgrade-sql-server-management-tools.md

Latest commit

 

History

History
46 lines (31 loc) · 4.43 KB

upgrade-sql-server-management-tools.md

File metadata and controls

46 lines (31 loc) · 4.43 KB
title Upgrade SQL Server Management Tools
description This article describes support for upgrading SQL Server Management Tools and management components, such as SQL Server Agent.
author rwestMSFT
ms.author randolphwest
ms.date 06/03/2025
ms.service sql
ms.subservice install
ms.topic upgrade-and-migration-article
helpviewer_keywords
management tools, upgrading
monikerRange >=sql-server-2016

Upgrade SQL Server Management Tools

[!INCLUDE SQL Server -Windows Only]

[!INCLUDE ssnoversion] supports upgrade from [!INCLUDE sql2008-md] and later versions. This article documents support and behavior for upgrading [!INCLUDE ssNoVersion] Management Tools and management components such as [!INCLUDE ssNoVersion] Agent, Database Mail, Maintenance Plans, XPStar, and XPWeb.

For local installations, you must run [!INCLUDE ssNoVersion] Setup as an administrator. If you run [!INCLUDE ssNoVersion] Setup from a remote share, you must use a domain account that has read and execute permissions on the remote share.

Known upgrade issues

  • Consider the following issues before you upgrade to [!INCLUDE ssnoversion]:

  • All TSX servers should be upgraded before the MSX server is upgraded. For more information about MSX/TSX in [!INCLUDE ssNoVersion], see Automated Administration Across an Enterprise.

  • All components in an instance of [!INCLUDE ssNoVersion] must be upgraded at the same time. Version numbers of the [!INCLUDE ssDE], [!INCLUDE ssASnoversion], and [!INCLUDE ssRSnoversion] components must be the same in an instance of [!INCLUDE ssnoversion].

  • You can add components to an existing installation of [!INCLUDE ssNoVersion] at the time that you upgrade to [!INCLUDE ssnoversion]. For more information, see Upgrade SQL Server Using the Installation Wizard (Setup).

  • [!INCLUDE ssNoVersion] Client Tools, such as [!INCLUDE ssManStudioFull], [!INCLUDE ssSqlProfiler], the [!INCLUDE ssDE] Tuning Advisor, sqlcmd, and osql aren't upgraded to [!INCLUDE ssnoversion]. Instead, Client Tools run side-by-side with tools from previous [!INCLUDE ssNoVersion] versions. [!INCLUDE ssnoversion] supports importing settings from earlier versions of [!INCLUDE ssNoVersion] Client Tools.

  • Authentication from [!INCLUDE ssNoVersion] Agent to [!INCLUDE ssNoVersion] is updated from [!INCLUDE ssNoVersion] Authentication to Windows Authentication during upgrade. [!INCLUDE ssNoVersion] Authentication isn't supported in [!INCLUDE ssnoversion].

  • Data for jobs and alerts are preserved during upgrade to [!INCLUDE ssnoversion].

  • If SQLMail is being used in the instance to be upgraded, associated XPs are supported and enabled after the upgrade. Otherwise, they're off.

  • Database Mail is upgraded with the [!INCLUDE ssDE] component of [!INCLUDE ssnoversion]. By default, Database Mail is off after upgrade. Any schema updates should be reconciled with an update script after upgrade.

Related content