Skip to content

upgrade-sql-server-management-tools.md

Latest commit

 

History

History
48 lines (34 loc) · 4.38 KB

upgrade-sql-server-management-tools.md

File metadata and controls

48 lines (34 loc) · 4.38 KB
title Upgrade SQL Server Management Tools | Microsoft Docs
ms.custom
ms.date 03/06/2017
ms.prod sql-server-2014
ms.reviewer
ms.technology install
ms.topic conceptual
helpviewer_keywords
management tools, upgrading
ms.assetid 1dab50b9-d16c-49a1-9ecc-af72adb6c378
author stevestein
ms.author sstein
manager craigg

Upgrade SQL Server Management Tools

[!INCLUDEssCurrent] supports upgrade from [!INCLUDEssVersion2005] and later. This topic documents support and behavior for upgrading [!INCLUDEssNoVersion] Management Tools and management components such as [!INCLUDEssNoVersion] Agent, Database Mail, Maintenance Plans, XPStar, and XPWeb.

Important

For local installations, you must run [!INCLUDEssNoVersion] Setup as an administrator. If you run [!INCLUDEssNoVersion] 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 [!INCLUDEssCurrent]:

For all upgrade scenarios:

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

  • All components in an instance of [!INCLUDEssNoVersion] must be upgraded at the same time. Version numbers of the [!INCLUDEssDE], [!INCLUDEssASnoversion], and [!INCLUDEssRSnoversion] components must be the same in an instance of [!INCLUDEssCurrent].

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

  • [!INCLUDEssNoVersion] Client Tools, such as [!INCLUDEssManStudioFull], [!INCLUDEssSqlProfiler], the [!INCLUDEssDE] Tuning Advisor, sqlcmd, and osql are not upgraded to [!INCLUDEssCurrent]. Instead, Client Tools run side-by-side with tools from previous [!INCLUDEssNoVersion] versions. [!INCLUDEssCurrent] supports importing settings from earlier versions of [!INCLUDEssNoVersion] Client Tools.

  • Authentication from [!INCLUDEssNoVersion] Agent to [!INCLUDEssNoVersion] will be updated from [!INCLUDEssNoVersion] Authentication to Windows Authentication during upgrade. [!INCLUDEssNoVersion] Authentication is not supported in [!INCLUDEssCurrent].

  • Data for jobs and alerts will be preserved during upgrade to [!INCLUDEssCurrent].

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

  • Database Mail, also known as SQLiMail, will be upgraded with the [!INCLUDEssDE] component of [!INCLUDEssCurrent]. By default, Database Mail will be off after upgrade. Any schema updates should be reconciled with an update script after upgrade.

See Also

Supported Version and Edition Upgrades
Backward Compatibility
Upgrade to SQL Server 2014 Using the Installation Wizard (Setup)