SQL SERVER升级2017

摘要

本文只介绍了SQL SERVER升级到2017(在简单环境下),分为开始升级前的检查事项,升级操作步骤,升级后对新实例的配置。

检查事项

1.检查当前版本是否可以升级到2017

SQL Server 2017 (14.x) supports upgrade from the following versions of SQL Server:

  • SQL Server 2008 SP4 or later
  • SQL Server 2008 R2 SP3 or later
  • SQL Server 2012 SP2 or later
  • SQL Server 2014 or later
  • SQL Server 2016 or later

2.检查当前服务器及实例配置是否满足升级条件

  • Before upgrading from one edition of SQL Server 2017 (14.x) to another, verify that the functionality you are currently using is supported in the edition to which you are moving.
  • Before upgrading SQL Server, enable Windows Authentication for SQL Server Agent and verify the default configuration: that the SQL Server Agent service account is a member of the SQL Server sysadmin group.
  • To upgrade to SQL Server 2017 (14.x), you must be running a supported operating system. For more information, see Hardware and Software Requirements for Installing SQL Server.
  • Upgrade will be blocked if there is a pending restart.
  • Upgrade will be blocked if the Windows Installer service is not running.

不支持的情况

  • Cross-version instances of SQL Server 2017 (14.x) are not supported. Version numbers of the Database Engine, Analysis Services, and Reporting Services components must be the same in an instance of SQL Server 2017 (14.x).
  • SQL Server 2017 (14.x) is only available for 64-bit platforms. Cross-platform upgrade is not supported. You cannot upgrade a 32-bit instance of SQL Server to native 64-bit using SQL Server Setup. However, you can back up or detach databases from a 32-bit instance of SQL Server, and then restore or attach them to a new instance of SQL Server (64-bit) if the databases are not published in replication. You must re-create any logins and other user objects in master, msdb, and model system databases.
  • You cannot add new features during the upgrade of your existing instance of SQL Server. After you upgrade an instance of SQL Server to SQL Server 2017 (14.x), you can add features by using the SQL Server 2017 (14.x) Setup. For more information, see Add Features to an Instance of SQL Server (Setup).
  • Failover Clusters are not supported in WOW mode.

升级步骤

  1. Insert the SQL Server installation media, and from the root folder, double-click Setup.exe. To install from a network share, move to the root folder on the share, and then double-click Setup.exe.
  2. The Installation Wizard starts the SQL Server Installation Center. To upgrade an existing instance of SQL Server, click Installation in the left-hand navigation area, and then click Upgrade from... previous versions of SQL Server.
  3. On the Product Key page, click an option to indicate whether you are upgrading to a free edition of SQL Server, or whether you have a PID key for a production version of the product. For more information, see Editions and Components of SQL Server 2016 and Supported Version and Edition Upgrades.
  4. On the License Terms page, review the license agreement and, if you agree, select the I accept the license terms check box, and then click Next. To help improve SQL Server, you can also enable the feature usage option and send reports to Microsoft.
  5. In the Global Rules window, the setup procedure will automatically advance to the Product Updates window if there are no rule errors.
  6. The Microsoft Update page will appear next if the Microsoft Update check box in Control Panel\All Control Panel Items\Windows Update\Change settings is not checked. Putting a check in the Microsoft Update page will change the computer settings to include the latest updates when you scan for Windows Update.
  7. On the Product Updates page, the latest available SQL Server product updates are displayed. If you don't want to include the updates, clear the Include SQL Server product updates check box. If no product updates are discovered, SQL Server Setup does not display this page and auto advances to the Install Setup Files page.
  8. On the Install Setup Files page, Setup provides the progress of downloading, extracting, and installing the Setup files. If an update for SQL Server Setup is found, and is specified to be included, that update will also be installed.
  9. In the Upgrade Rules window, the setup procedure will automatically advance to the Select instance window if there are no rule errors.
  10. On the Select Instance page, specify the instance of SQL Server to upgrade. To upgrade Management tools and shared features, select Upgrade shared features only.
  11. On the Select Features page, the features to upgrade will be preselected. A description for each component group appears in the right pane after you select the feature name.

The prerequisites for the selected features are displayed on the right-hand pane. SQL Server Setup will install the prerequisite that are not already installed during the installation step described later in this procedure.

 Note

If you have opted to upgrade the shared features by selecting <Upgrade shared features only> on the Select Instance page, all the shared features are preselected on the Feature Selection page. All the shared components are upgraded at the same time.

  1. On the Instance Configuration page, specify the Instance ID for the instance of SQL Server.

Instance ID - By default, the instance name is used as the Instance ID. This is used to identify installation directories and registry keys for your instance of SQL Server. This is the case for default instances and named instances. For a default instance, the instance name and instance ID would be MSSQLSERVER. To use a non-default instance ID, provide a value for the Instance ID textbox.

All SQL Server service packs and upgrades will apply to every component of an instance of SQL Server.

Installed instances - The grid will show instances of SQL Server that are on the computer where Setup is running. If a default instance is already installed on the computer, you must install a named instance of SQL Server.

  1. Work flow for the rest of this article depends on the features that you have specified for your installation. You might not see all the pages, depending on your selections.
  2. On the Server Configuration - Service Accounts page, the default service accounts are displayed for SQL Server services. The actual services that are configured on this page depend on the features that you are upgrading.

Authentication and login information will be carried forward from the previous instance of SQL Server. You can assign the same login account to all SQL Server services, or you can configure each service account individually. You can also specify whether services start automatically, are started manually, or are disabled. Microsoft recommends that you configure service accounts individually so that SQL Server services are granted the minimum permissions they have to have to complete their tasks. For more information, see Configure Windows Service Accounts and Permissions.

To specify the same login account for all service accounts in this instance of SQL Server, provide credentials in the fields at the bottom of the page.

Security Note Do not use a blank password. Use a strong password.

When you are finished specifying login information for SQL Server services, click Next.

  1. On the Full-Text Search Upgrade Options page, specify the upgrade options for the databases being upgraded. For more information, see Full-Text Search Upgrade Options.
  2. The Feature Rules window will automatically advance if all rules pass.
  3. The Ready to Upgrade page displays a tree view of installation options that were specified during Setup. To continue, click Install. SQL Server Setup will first install the required prerequisites for the selected features followed by the feature installation.
  4. During installation, the progress page provides status so that you can monitor installation progress as Setup continues.
  5. After installation, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the SQL Server installation process, click Close.
  6. If you are instructed to restart the computer, do so now. It is important to read the message from the Installation Wizard when you have finished with Setup. For more information about Setup log files, see View and Read SQL Server Setup Log Files.

配置新实例

  • Register your servers - Upgrade removes registry settings for the previous instance of SQL Server. After you upgrade, you must reregister your servers.
  • Update statistics - To help optimize query performance, we recommend that you update statistics on all databases following upgrade. Use the sp_updatestats stored procedure to update statistics in user-defined tables in SQL Server databases.
  • Configure your new SQL Server installation - To reduce the attackable surface area of a system, SQL Server selectively installs and enables key services and features. For more information about surface area configuration, see the readme file for this release.

SQL SERVER升级2017的更多相关文章

  1. sql server升级打补丁

    原本:https://blog.csdn.net/kk185800961/article/details/72436415 sql server升级 sql server打补丁 sql server升 ...

  2. [转帖]SQL Server 2000~2017补丁包

    SQL Server 2000~2017补丁包 https://www.cnblogs.com/VicLiu/p/11510510.html 最新更新 Product Version Latest S ...

  3. SQL Server 2000~2017补丁包

    最新更新 Product Version Latest Service Pack Latest GDR Update Latest Cumulative Update CU Release Date ...

  4. 【SQL SERVER】2017 Developer 安装教程

    官网下载地址:https://www.microsoft.com/zh-cn/sql-server/sql-server-downloads 1.下载之后双击exe文件,选择基本 自定义都行 2.选择 ...

  5. 迁移数据库数据到SQL Server 2017

      概述 本篇我们将利用DMA一步一步实现SQL Server 的迁移.帮助大家理解现在的SQL Server与新版本的融合问题,同时需要我们做哪些操作来实现新版本的升级或者迁移. SQL Serve ...

  6. 微软Ignite大会我的Session(SQL Server 2014 升级面面谈)PPT分享

       我在首届微软技术大会的Session分享了一个关于SQL Server升级的主题,现在将PPT分享出来.     您可以点击这里下载PPT.     也非常感谢微软中国邀请我进行这次分享.

  7. SQL Server 2008 R2升级到SQL Server 2012 SP1

    1.建议对生产环境对的数据库升级之前做好备份,以防不测. 2.从SQL Server 2008 R2 升级到SQL Server 2012 SP1,需要先安装SQL Server 2008 R2 的S ...

  8. Sql Server 2008R2升级 Sql Server 2012 问题

    环境: Windows server 2008 r2 Standard +SqlServer2008R2  内网环境需要升级为SQL server 2012 升级安装时提示版本不支持 网上查询相关问题 ...

  9. SQL Server 2012 数据库数据导出为脚本

    转自:http://blog.csdn.net/ituff/article/details/8265822 将高版本的的SQL Server数据库移到低版本的SQL Server是一件十分蛋疼的事,最 ...

随机推荐

  1. revit 碰撞检测相关

    Revit二次开发:由房间获取房间的墙     之前用的方法是由房间边界构成的Solid,计算与该Solid相交的Element,然后判断是否为墙.相对来说这个方法比较通用,可以检索出房间的楼板.窗户 ...

  2. 转:webpack代码压缩优化

    压缩代码 18 天前30前端开发 压缩 JavaScript 修改 JavaScript 压缩处理器 其他压缩 JavaScript 的方法 加快 JavaScript 执行速度 作用域提升 预执行 ...

  3. Java8 特性

    1.jdk8的特性stream().map() 2.Java8中用Lambda表达式的groupBy合并多个相同属性的对象集合 3.Java8 Stream 语法详解 & 用法实例

  4. rtmp_specification_1.0

    Copyright Adobe Systems Incorporated H. Parmar, Ed. M. Thornburgh, Ed. Adobe December 21, 2012 Adobe ...

  5. Gerrit - Gerrit与GitLab集成

    1 - 简介 虽然Gerrit 本身提供 Code Review和 Git 仓库的两大功能,但实际上很多项目用的是其他的Git仓库,例如GitLab和GitHub. 一般情况下,Gerrit位于最终代 ...

  6. git worktree 稀疏检出(sparseCheckout)

    稀疏检出配置: git config core.sparsecheckout true echo another_folder/xxxx/ >> .git/info/sparse-chec ...

  7. java中的内存分配问题

    class A{ int i; int j; } clsaa demo{ public static void main(String[] args){ A aa = new A(); A aa; / ...

  8. 【LOJ2292】[THUSC2016]成绩单(区间DP)

    题目 LOJ2292 分析 比较神奇的一个区间 DP ,我看了很多题解都没看懂,大约是我比较菜罢. 先明确一下题意:abcde 取完 c 后变成 abde ,可以取 bd 这样取 c 后新增的连续段. ...

  9. Endpoint is unreachable and there is no snapshot available for offline browsing

    docker Portainer配置的时候出现这个错误:Endpoint is unreachable and there is no snapshot available for offline b ...

  10. Anaconda的pip加速下载命令

    pip config set global.index-url https://pypi.tuna.tsinghua.edu.cn/simple