Skip to content

overview-of-sql-server-servicing-installation.md

Latest commit

 

History

History
144 lines (88 loc) · 16.9 KB

overview-of-sql-server-servicing-installation.md

File metadata and controls

144 lines (88 loc) · 16.9 KB
title Overview of SQL Server Servicing Installation | Microsoft Docs
ms.custom
ms.date 06/13/2017
ms.prod sql-server-2014
ms.reviewer
ms.technology database-engine
ms.topic conceptual
ms.assetid 6a9fd19b-2367-4908-b638-363b1e929e1e
author mashamsft
ms.author mathoma
manager craigg

Overview of SQL Server Servicing Installation

You can apply an update to any installed [!INCLUDEssCurrent] component with a [!INCLUDEssCurrent] servicing update. If the version level of an existing [!INCLUDEssCurrent] component is later than the update version level, the Setup program will exclude it from the update. For more information on applying a servicing update, see Install SQL Server 2014 Servicing Updates.

The following considerations apply when you install [!INCLUDEssCurrent] updates:

  • All features that belong to an instance of [!INCLUDEssNoVersion] must be updated at the same time. For example, when you update the [!INCLUDEssDE], you must also update [!INCLUDEssASnoversion] and [!INCLUDEssRSnoversion] components if they are installed as part of the same instance of [!INCLUDEssNoVersion]. Shared features, such as Management Tools, [!INCLUDEssBIDevStudioFull], and [!INCLUDEssNoVersion][!INCLUDEssISnoversion], must always be updated to the most recent update. If a component or instance in the feature tree is not selected, the component or instance will not be updated.

  • By default, [!INCLUDEssCurrent] update log files are saved to %Program Files%\[!INCLUDEmsCoName][!INCLUDEssNoVersion]\120\Setup Bootstrap\LOG\.

  • [!INCLUDEssNoVersion] setup can now integrate an update with the original media to run the original media and the update at the same time. For more information, see What's New in SQL Server Installation.

  • Before you apply a [!INCLUDEssCurrent] servicing update, we recommend that you consider backing up your data.

  • [!INCLUDEssNoVersion] updates are available through [!INCLUDEmsCoName] Update. We recommend that you scan for updates regularly to keep your instance of [!INCLUDEssNoVersion] updated and secure. [!INCLUDEssCurrent] SP1 is being provided as a complete [!INCLUDEssNoVersion] Installation. Rather than providing the Service Pack in the standard Patch executable package to be applied to [!INCLUDEssCurrent] RTM instances, for this release, an installation package (consisting of 2 files) is provided. When executed, this will install a new instance of [!INCLUDEssNoVersion] with SP1 pre-installed.

Requirements and Known Issues

The recommended disk space requirements are approximately 2.5 times the size of the package to install, download, and extract the package. After installing a service pack, you can remove the downloaded package. Any temporary files are removed automatically.

Review the known issues: For more information about the known issues for the current release, see the corresponding release notes topic here: SQL Server Release Notes.

Installation Overview

This section discusses the [!INCLUDEssCurrent] installation for cumulative updates and service packs, including how to do the following:

  • Prepare for a [!INCLUDEssCurrent] update installation

  • Install [!INCLUDEssCurrent] updates

  • Restart services and applications

Prepare for a [!INCLUDEssCurrent] Update Installation

We strongly recommend that you do the following before you install [!INCLUDEssCurrent] updates:

  • Back up your [!INCLUDEssNoVersion] system databases - Before you install [!INCLUDEssCurrent] updates, back up the master, msdb, and model databases. Installing a [!INCLUDEssCurrent] update changes these databases, making them incompatible with earlier versions of [!INCLUDEssCurrent]. Backups of these databases are required if you decide to reinstall [!INCLUDEssCurrent] without these updates.

    It is also prudent to back up your user databases.

    [!IMPORTANT]
    When you apply updates to instances of [!INCLUDEssNoVersion] that participate in a replication topology, you must back up your replicated databases together with your system databases before you apply the update.

  • Back up your [!INCLUDEssASnoversion] databases, configuration file, and repository - Before you update an instance of [!INCLUDEssASnoversion], you should back up the following:

    • [!INCLUDEssASnoversion] databases. By default, these are installed to C:\Program Files\[!INCLUDEmsCoName][!INCLUDEssNoVersion]\MSAS12.<InstanceID>\OLAP\Data\. For WOW installation, the default path is C:\ProgramFiles (x86)\ [!INCLUDEmsCoName][!INCLUDEssNoVersion]\MSAS12.<InstanceID>\OLAP\Data\.

    • [!INCLUDEssASnoversion] configuration setting in the msmdsrv.ini configuration file. By default, this is located in the C:\Program Files\[!INCLUDEmsCoName][!INCLUDEssNoVersion]\MSAS12.<InstanceID>\OLAP\Config\ directory.

    • (Optional) The database that contains the [!INCLUDEssASnoversion] repository. This step is required only if [!INCLUDEssASnoversion] was configured to work with the Decision Support Objects (DSO) library.

    [!NOTE]
    Failure to back up your [!INCLUDEssASnoversion] databases, configuration file, and repository will prevent you from reverting an updated instance of [!INCLUDEssASnoversion] to the earlier version.

  • Verify that the system databases have sufficient free space - If the autogrow option is not selected for the master and msdb system databases, these databases each must have at least 500 KB of free space. To verify that the databases have sufficient space, run the sp_spaceused system stored procedure on the master and msdb databases. If the unallocated space in either database is less than 500 KB, increase the size of the database.

  • Stop Services and Applications - To avoid a possible restart of the system, stop all applications and services that make connections to the instances of [!INCLUDEssNoVersion] that are being upgraded, before installing [!INCLUDEssCurrent] updates. These include [!INCLUDEssManStudioFull], [!INCLUDEssBIDevStudioFull]. For more information, see Start, Stop, Pause, Resume, Restart the Database Engine, SQL Server Agent, or SQL Server Browser Service.

    [!NOTE]
    You cannot stop services in a failover cluster environment. For more information, see the failover cluster installation section later in this topic.

  • To eliminate the requirement to restart your computer after update installation, Setup will show a list of processes that are locking files. If the update Setup program must end a service during installation, it will restart the service after the installation finishes.

  • If Setup determines that files are locked during installation, you might have to restart your computer after the installation finishes. If it is required, Setup prompts you to restart your computer.

Install [!INCLUDEssCurrent] Updates

This section describes the installation process.

Important

[!INCLUDEssCurrent] updates must be installed under an account that has administrative privileges on the computer where they will be installed. For local installations, you must run Setup as an administrator. If you install [!INCLUDEssNoVersion] from a remote share, you must use a domain account that has read and execute permissions on the remote share.

Starting a [!INCLUDEssCurrent] Update

To install a [!INCLUDEssCurrent] update, run the self-extracting package file.

Cumulative update package (CU): <SQLServer2014>-KBxxxxxx-PPP.exe

Service pack package (PCU): <SQLServer2014><SPx> -KBxxxxxx-PPP-LLL.exe

  • x indicated service pack number

  • PPP indicates the specific platform.

  • LLL indicates the character abbreviation for the [!INCLUDEssNoVersion] language, for example: LLL for English is ENU.

To apply updates to [!INCLUDEssCurrent] components that are part of a failover cluster, see the section for failover cluster installation. For more information about how to run an update installation in unattended mode, see Install SQL Server 2014 from the Command Prompt.

Product Updates in [!INCLUDEssCurrent] Installation

Product Update is a feature in [!INCLUDEssCurrent] Setup. It integrates the latest product updates with the main product installation so that the main product and its applicable updates are installed at the same time. Product Update can search [!INCLUDEmsCoName] Update, Windows Server Update Services (WSUS), a local folder, or a network share for applicable updates. After Setup finds the latest versions of the applicable updates, it downloads and integrates them with the current [!INCLUDEssNoVersion] setup process. Product Update can pull in a cumulative update, service pack, or service pack plus cumulative update. Product Update functionality is an extension of the Slipstream functionally that was available in [!INCLUDEssKatmai] PCU1.

Updating a Prepared Image of [!INCLUDEssNoVersion]

You can apply an update to an unconfigured prepared instance of [!INCLUDEssNoVersion] without completing the configuration of the prepared instance. Different ways of applying an update to a prepared instance of [!INCLUDEssNoVersion] are explained below:

  • Updating a previously prepared instance of [!INCLUDEssNoVersion]

    Updates to a prepared instance can be applied to prior to configuration. The update package detects that the instance is in the prepared state and apply the patch to the prepared instance, without completing the configuration.

  • Updates to a prepared instance using [!INCLUDEmsCoName] Update:

    You can apply updates to a prepared instance of [!INCLUDEssNoVersion] through [!INCLUDEmsCoName] Update. The [!INCLUDEmsCoName] Update package will detect that the instance is in the prepared state and apply the patch to the prepare instance without completing the configuration.

If you are updating a prepared image of [!INCLUDEssNoVersion], you will need to specify the InstanceID parameter. For more information and sample syntax, see Installing Updates from the Command Prompt.

Updating a Completed Image of [!INCLUDEssNoVersion]

Updating a completed and configured instance of [!INCLUDEssNoVersion] follows the same processes as any other installed instances of [!INCLUDEssNoVersion].

Rebuilding a [!INCLUDEssCurrent] Failover Cluster Node

If you must rebuild a node in the failover cluster after updates were applied, follow these steps:

  1. Rebuild the node in the failover cluster. For more information about rebuilding a node, see Recover from Failover Cluster Instance Failure.

  2. Run the original [!INCLUDEssCurrent] Setup program to install [!INCLUDEssCurrent] on the failover cluster node.

  3. Run [!INCLUDEssCurrent] updates Setup on the node that you have added.

Restart Services and Applications

When the Setup program is finished, it might prompt you to restart the computer. After the system restarts, or after the Setup program finishes without requesting a restart, use the Services node in Control Panel to restart the services that you stopped before you applied the [!INCLUDEssCurrent] updates. This includes services such as Distributed Transaction Coordinator and the [!INCLUDEmsCoName] Search services, or instance-specific equivalents.

Restart the applications that you closed before you ran [!INCLUDEssCurrent] update Setup. You might also want to make another backup of the upgraded master, msdb, and model databases immediately after successful installation.

Uninstalling Updates from [!INCLUDEssCurrent]

You can uninstall [!INCLUDEssCurrent] cumulative updates or service packs from Programs and Features in Control Panel. To view the list of updates installed, open Installed Updates by clicking the Start button, clicking Control Panel, clicking Programs, and then, under Programs and Features, clicking View installed updates. Each cumulative update is listed separately. However, when a service pack is installed that is higher than the cumulative updates, the cumulative update entries are hidden and become available only if you uninstall the service pack.

To uninstall any service packs and updates, you must start with the latest update or service pack applied to the instance of [!INCLUDEssNoVersion] and work backward. In each of the following examples, [!INCLUDEssNoVersion] ends up with Cumulative Update 1 after uninstall has been completed for the other service packs or updates:

  • For an instance of [!INCLUDEssCurrent] with Cumulative Update 1 and SP1 installed, uninstall SP1.

  • For an instance of [!INCLUDEssCurrent] with Cumulative Update 1, SP1, and Cumulative Update 2 installed, uninstall Cumulative Update 2 first and then uninstall SP1.

See Also

Install SQL Server 2014 from the Command Prompt
Install SQL Server 2014 Servicing Updates
Validate a SQL Server Installation
View and Read SQL Server Setup Log Files