Upgrade to and Installation of SQL Server 2016 in

Upgrade and Installation Guide
PUBLIC
Document Version: 1.30 – 2017-12-11
Upgrade to and Installation of SQL Server 2016 in an
SAP Environment
Content
1
Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3
General Requirements and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System. . . . . . . . . . . . . . . . . . . 9
4.1
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
4.2
General Prerequisites for Upgrading SQL Server to SQL Server 2016. . . . . . . . . . . . . . . . . . . . . . . . . 9
4.3
Upgrading SQL Server to SQL Server 2016 for an Existing Non-High-Availability SAP System. . . . . . . 10
4.4
Upgrading SQL Server Failover Cluster to SQL Server 2016 Failover Cluster. . . . . . . . . . . . . . . . . . . 14
5
Installing SQL Server 2016 for a New SAP System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2
Installing the SQL Server Database Software Automatically with SQL4SAP. . . . . . . . . . . . . . . . . . . . 21
5.3
Installing the SQL Server 2016 Database Server Software Manually. . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4
Installing the SQL Server 2016 Failover Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.5
Installing the SQL Server 2016 Client Software Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
6
Setting the SQL Server Agent Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Content
1
Document History
Note
Before you start the implementation, make sure you have the latest version of this document.
Table 1:
Version
Date
Description
1.30
2017-12-11
Updated version
Minor changes
1.20
1.10
2017-11-17
2016-10-14
Updated version
●
Updated links
●
Minor changes in entire document
Updated version
Directory name on RDBMs media cor­
rected in various sections
1.00
2016-10-04
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Document History
Initial version
PUBLIC
3
2
Introduction
This document describes the upgrade to or installation of SQL Server 2016 for an SAP system.
Caution
This guide contains very customized configuration settings only used by some SAP applications, not all SAP
applications. Following the steps in this guide for applications other than which it is intended will cause
problems, and most likely errors, in other applications. Please see General Requirements and Restrictions
[page 6] for more information.
Note
With SQL Server 2016, Microsoft changed the default for the Customer Experience Improvement Program
(CEIP). The CEIP is now enabled by default.
SQL4SAP [page 21] will disable CEIP for the SQL Server instance after the installation.
For more information about how to disable CEIP manually, read the Microsoft KB 3153756, which is available
at (https://support.microsoft.com/en-us/kb/3153756 ).
You have the following options to use SQL Server 2016 in an SAP environment:
● You upgrade an existing SQL Server 2008, SQL Server 2008 R2, or SQL Server 2012, or SQL Server 2014
instance that is already running an SAP system to SQL Server 2016. SAP does not support any upgrade
method other than that described here. For more information, see Upgrading SQL Server to SQL Server
2016 for an Existing SAP System [page 9].
Caution
Before you upgrade SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 to
SQL Server 2016, make sure that you import the required support package stacks [page 6] to your
system. Otherwise, the upgraded system does not function correctly with SQL Server 2016.
● You install SQL Server 2016 for a new SAP system. For more information, see Installing SQL Server 2016
for a New SAP System [page 21].
You have the following options to install SQL Server 2016 for a new SAP system.
○ You install SQL Server 2016 for a non-high-availability (non-HA) SAP system
You can either install the SQL Server database software using a special script named SQL4SAP
provided by SAP, or you can install it manually.
Note
We highly recommend that you perform any new installation of an SQL Server 2016 instance for a
non-HA system with the SQL4SAP script. The script is located on the SQL Server 2016 RDBMS
medium that is shipped with the SAP products.
○ You install SQL Server 2016 for a high availability (HA) SAP system
4
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Introduction
Note
If you want to install the SQL Server database software for an HA system, you must install the SQL
Server database software manually. You cannot use the SQL4SAP script.
● You perform a system copy of an SAP system. For more information, see SAP Note 2201060
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Introduction
.
PUBLIC
5
3
General Requirements and Restrictions
Required SQL Server 2016 Installation Medium
Before SQL Server 2014, SAP has always prepared and provided a single SQL Server RDBMS medium to all
customers regardless of whether they bought the SQL Server license from SAP or from another vendor. As of
SQL Server 2014, there are two SQL Server RDBMS media available for SAP customers. Besides these two
media delivered by SAP, an SQL Server installation medium is also available. This is officially delivered by
Microsoft or authorized dealers.
Table 2: Available SQL Server 2016 Media
Media
Description
SQL Server RDBMS medium (for run­
Contains both the SQL4SAP framework and the SQL Server installation medium
time customers)
(see below) to install the SQL Server database. The structure of this medium is
identical to SAP medium delivered for previous SQL Server releases. The medium
can be used by customers who purchase their SQL Server license from SAP.
SQL Server RDBMS medium (for non-
Contains the SQL4SAP framework but not the SQL Server installation medium
runtime customers)
(see below). During the installation with SQL4SAP, you are prompted to provide
the location of the SQL Server installation medium. The medium can be used by
customers who do not purchase their SQL Server license from SAP.
SQL Server installation medium
SQL Server installation medium that is officially delivered by Microsoft or author­
ized dealers for the installation of the Microsoft SQL Server 2016 database.
Required SAP Notes
Read the following SAP notes before using SQL Server 2016:
Table 3: General SAP Notes
Note Number
Title
Remarks
2201060
Setting Up Microsoft SQL Server 2016
Provides the latest information about
the upgrade to and installation of SQL
Server 2016.
2201059
Release planning for Microsoft SQL
Provides release planning information
Server 2016
about SQL Server 2016, including the
minimum SAP support package stack­
levels
6
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
General Requirements and Restrictions
Note Number
Title
Remarks
1252970
Triggers on SAP tables
In general, SAP does not support any
triggers on SAP tables in SQL Server. If,
due to application-specific require­
ments, you have to use triggers on SAP
tables in SQL Server, follow the guide­
lines stated in this SAP note.
2312935
2116639
Configuration Parameters for SQL
Provides information about how to con­
Server 2016
figure SQL Server for your SAP system
SQL Server 2014 columnstore docu­
Provides attached documentation on
mentation
In-Memory Optimized Columnstore
with SAP BW and SAP BW Columnstore
Optimized Flat Cube
Required Support Package Stacks
For more information about the minimum support package stack levels to run on SQL Server 2016 for your SAP
system, see SAP note 2201059 .
Note
We recommend that you apply all available SAP_BASIS support package stacks before using SQL Server
2016 in a production system.
General Requirements and Restrictions for Using SQL Server 2016
Note the following general requirements and restrictions, which both apply when using SQL Server 2016 for a
non-HA or a HA SAP system:
● SQL Server 2016 is supported on Windows Server 2012 and higher
● SQL Server 2016 is only supported on Windows x64.
● SAP releases prior to SAP NetWeaver 7.0 are not supported to run on SQL Server 2016. For more
information, see SAP Note 2201060 .
● Not all combinations of SQL Server 2016 and Windows are supported by all SAP products.
For up-to-date information on supported releases of SAP systems with SQL Server 2016, see the Product
Availability Matrix (PAM) at:
http://support.sap.com/pam
● You must only use the SAP upgrade and installation tools according to the instructions and for the
purposes described in the SAP upgrade and installation documentation. Improper use of the SAP upgrade
and installation tools can damage files and already upgraded or installed systems.
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
General Requirements and Restrictions
PUBLIC
7
● Only the SQL Server 2016 upgrade and installation procedures described in this guide have been tested by
SAP. All other upgrade and installation procedures described in the SQL Server Books Online have not
been tested by SAP.
● When installing or upgrading to SQL Server 2016, make sure that you have enough free disk space
available on the system drive for:
○ .Net Framework
○ SQL Server client tools
○ SQL Server instance
○ Temporary space during the installation
The required disk space depends on the type of SQL Server components already installed or to be
installed. It also depends on the system. You might require up to 6 GB free disk space on the system drive.
Additional Requirements and Restrictions for Using SQL Server 2016 in a
High-Availability SAP System
In addition to the general requirements and restrictions listed above, the following requirements and
restrictions apply for the upgrade to and installation of SQL Server 2016 in a high-availability (HA) system.
Note
For a complete list of the restrictions and more information, see:
SQL Server 2016 Books Online at:
http://msdn.microsoft.com/en-us/library/ms130214(v=sql.130).aspx
● Make sure that you have not applied NTFS compression to the disk where you install the SQL Server
software.
● Make sure that you have not installed anti-virus software on your Microsoft failover cluster.
For more information, see the Microsoft KB article Antivirus software that is not cluster-aware may cause
problems with Cluster Services, which is available at:
http://support.microsoft.com/kb/250355/en-us .
● Check the system logs of the nodes for any errors before starting the installation.
● For all hardware and software requirements for installing SQL Server, check the following link
http://msdn.microsoft.com/en-us/library/ms143506(v=sql.130).aspx
8
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
General Requirements and Restrictions
4
Upgrading SQL Server to SQL Server
2016 for an Existing SAP System
4.1
Introduction
The following sections describe how to upgrade SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or
SQL Server 2014 to SQL Server 2016.
Caution
The upgrade procedure in this document is only valid if the source SQL Server database software was
installed by the SAP script or manually as described in the relevant Upgrade and Installation Guide.
4.2
General Prerequisites for Upgrading SQL Server to SQL
Server 2016
If you want to upgrade SQL Server 2008 (R2), SQL Server 2012, or SQL Server 2014 for an existing SAP
system, you must meet the following prerequisites:
● You use an SAP system based on SAP NetWeaver with the minimum recommended support package stack
level for SQL Server 2016.
● If your SQL Server release is SQL Server 2014, make sure that you apply SP1 to the system before you
upgrade to SQL Server 2016.
● If your SQL Server release is SQL Server 2012, make sure that you apply SP2 to the system before you
upgrade to SQL Server 2016.
● If your SQL Server release is SQL Server 2008 R2, make sure that you apply SP3 to the system before you
upgrade to SQL Server 2016.
● If your SQL Server release is SQL Server 2008, make sure that you apply SP4 to the system before you
upgrade to SQL Server 2016.
● You have imported the latest SAP kernel patches, dbsl library, and support package stacks, making sure
that you apply at least the minimum level mentioned above.
You can find these patches on SAP Service Marketplace. For more information, see SAP Note 19466 .
● If you use a Java system, you have updated the JDBC driver as described in SAP Note 639702
● If you installed the SQL Server 2008 (R2), SQL Server 2012, or SQL Server 2014 database software with
the SQL4SAP script or manually, only the SQL Server features that are required for the operation of the
SAP application were installed.
If you installed additional SQL Server features, for example, Analysis Services, Report Services, Integration
Services and SQL Server Replication, check the SQL Server Books Online for any upgrade restrictions and
steps.
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
PUBLIC
9
● You have backed up your SQL Server database.
● You have shut down the SAP system.
Caution
● The upgrade will be blocked if there is a pending restart.
● The upgrade will be blocked if the Windows Installer service is not running.
● The upgrade will be blocked if performance counters are corrupt.
4.3
Upgrading SQL Server to SQL Server 2016 for an
Existing Non-High-Availability SAP System
Use
This section provides information about the upgrade of SQL Server 2008 (R2), SQL Server 2012, or SQL Server
2014 system to SQL Server 2016 in an existing non-high-availability system.
Caution
As of SQL Server 2008, SAP no longer supports 32-bit database servers or 32 bit application servers.
Prerequisites
You have met the general prerequisites mentioned above.
Procedure
1. Upgrade the SQL Server 2008 (R2), SQL Server 2012 or SQL Server 2014 instance to SQL Server 2016 as
follows:
1. Log on to the host as a local administrator.
2. Insert the SQL Server 2016 RDBMS medium in your media drive or copy it locally.
3. Change to the directory:
x64\EnterpriseEdition.
If you use the SQL Server RDBMS medium (for runtime customers), the SQL Server Setup is located in
the subdirectory x64\EnterpriseEdition. If you did not purchase your license from SAP, use the
official Microsoft SQL Server medium to start setup.exe.
4. Start the installation program with one of the following:
○ setup.exe
(if you want to upgrade to the SQL Server RTM build)
10
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
You also get the option to install the latest Service Pack (SP) and Cumulative Update (CU) via the
Windows update service.
○ setup.exe /Action=Upgrade /UpdateSource="<Drive>:
\<Upgrade_Source_Directory>"
where <Upgrade_Source_Directory> is the directory where you can copy the Service Pack
(SP) and Cumulative Update (CU) you want to upgrade to during the upgrade of the SQL Server.
For the Cumulative Update package, the initial download is a _zip.exe file. Make sure that you
unzip the package and copy the executable .exe to the Update Source directory.
Note
You can upgrade your SQL Server database either with the Service Pack and Cumulative Update as
the minimum required build (SP and CU) as specified in SAP Note 62988 , or with the latest
Service Pack and currently released Cumulative Update for the SQL Server product you want to
upgrade. For more information on how to set up the UpdateSource directory, see http://
msdn.microsoft.com/en-us/library/ms144259.aspx
.
5. Enter the required information as specified in the table below:
Note
The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL Server
\130\Setup Bootstrap\LOG\<YYYYMMDD_HHMM>. You find the summary of the setup log in
Summary.txt in the same directory.
Table 4: Input for the SQL Server 2016 Upgrade
Window
SQL Server Installation Center
Input
1.
Choose Installation.
2. Select Upgrade from a previous version of SQL
Server.
Note
This window does not appear, if you run setup.exe
with the parameter /UpdateSource.
Setup Support Rules
If there are no failed operations or warnings, choose OK.
Otherwise, first check the failed operations and warn­
ings.
Product Key
If this screen appears, enter the product key and
choose Next.
License Terms
Accept the Microsoft software license terms and
choose Next.
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
PUBLIC
11
Window
Input
Global Rules
Check the global rule errors and warnings.
If there are no errors, the setup automatically advances
to the next window.
Microsoft Update
Select the check-box and choose Next.
Product Updates
Displays the latest SQL Server updates, if available.
If there are no updates, the setup automatically advan­
ces to the next window.
Install Setup Files
The setup installs the setup files and product updates if
selected.
Upgrade Rules
Check the upgrade rule errors and warnings.
If there are no upgrade rule errors, the setup automati­
cally advances to the Select Instance window.
Select Instance
Select the SQL Server instance you want to upgrade.
To upgrade Management tools and shared features, se­
lect Upgrade features only.
Choose Next.
Select Features
Choose Next.
You cannot change the SQL Server features to be up­
graded.
Instance Configuration
Specify the instance ID for the instance of SQL Server.
By default, the instance name is used as the instance
ID.
Then choose Next.
Server Configuration
Leave the default values unchanged and choose Next.
Full-Text Upgrade
Select your option (see SQL Server Books Online for ad­
ditional information) and choose Next.
Feature Rules
Check the failed feature rules and warnings.
If there are no failed rules or warnings, the setup auto­
matically advances to the next window.
12
Ready to Upgrade
Check the summary list and choose Upgrade.
Upgrade Progress
Displays the upgrade progress
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
Window
Input
Complete
After the upgrade has been completed, the setup dis­
plays the status and a link to the log files…
Choose Close to finish the installation.
6. When you have finished the upgrade, check that the TCP/IP protocol in the SQL Server Configuration
Manager is enabled.
Search for SQL Server 2016 Configuration Manager to enable TCP/IP.
7. Restart SQL Server.
8. If you upgraded to the SQL Server 2016 RTM build, or if you want to install an additional Service Pack
and Cumulative Update, install them. For more information about the minimum required build, see
SAP Note 62988 .
2. Download and install the SQL Server Mangement Tools by selecting the option Install SQL Server
Management Tools in the SQL Server Installation center.
In SQL Server 2016, SQL Server Management Tools is a separate installation option. The installation of SQL
Server Management studio is a SAP support requirement.
3. Run the SAP tools for MS SQL Server.
The SAP tools for MS SQL Server perform the post-upgrade steps that are required for all SAP products
based on SAP NetWeaver running on SQL Server 2016.
For more information about how to use and where to download them, see SAP Note 683447 .
4. Start the SAP system.
5. Connect with a database administrator logon to the SQL Server 2016 Management Studio.
6. Open a new query window and execute the following commands:
use <SID> – where <SID> is your SAP database
go
EXEC sp_updatestats
go
It takes some time to replace the old SQL Server index statistics with new SQL Server 2016 statistics. You
can execute this while the SAP system is online.
7. If the page verify option is not set, change it with the following commands:
use master
go
alter database <SID> SET PAGE_VERIFY CHECKSUM;
go
8. Set the configuration for the SQL Server Agent [page 33].
9. If your system landscape is distributed and SAP application instances are installed on hosts other than the
database instance host, you need to install SQL Server 2016 client software on these hosts as described in
Installing the SQL Server 2016 Client Software Manually [page 32].
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
PUBLIC
13
4.4
Upgrading SQL Server Failover Cluster to SQL Server
2016 Failover Cluster
Use
This section provides information about the upgrade of SQL Server 2008 (R2), or SQL Server 2012, or SQL
Server 2014 failover cluster to SQL Server 2016 failover cluster in an existing high-availability (HA) system.
Caution
As of SQL Server 2008, SAP no longer supports 32-bit database servers or 32 bit application servers.
Prerequisites
● You have met the general prerequisites.
● You disable all trace flags set in the SQL Server.
● You check that the failover of the existing SQL Server installed in your cluster is working by moving the SQL
Server group between the cluster nodes before you perform the upgrade to SQL Server 2016.
● You review the following sections in SQL Server Books Online:
○ Before Installing Failover Clustering (http://msdn.microsoft.com/en-us/library/ms189910(v=sql.
130).aspx )
○ Preinstallation Checklist
Procedure
After having met all prerequisites on all nodes, start the failover cluster upgrade of the SQL Server instance to
SQL Server 2016.
Perform the following steps on all cluster nodes, beginning with the passive node:
1. Log on as a user who has administrator rights with permissions to log on as a service and to act as part of
the operating system on all nodes.
2. Insert the SQL Server 2016 RDBMS medium in your media drive or copy it locally.
3. Move all the cluster resources and groups to the first (active) cluster node.
4. Change to the directory:
x64\EnterpriseEdition.
If you use the SQL Server RDBMS medium (for runtime customers), the SQL Server Setup is located in the
subdirectory x64\EnterpriseEdition. If you did not purchase your license from SAP, use the official
Microsoft SQL Server medium to start setup.exe.
5. Start the installation program with one of the following:
○ setup.exe
(if you want to upgrade to the SQL Server RTM build)
14
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
You also get the option to install the latest Service Pack (SP) and Cumulative Update (CU) via the
Windows update service.
○ setup.exe /Action=Upgrade /UpdateSource="<Drive>:\<Upgrade_Source_Directory>"
where <Upgrade_Source_Directory> is the directory where you can copy the Service Pack (SP)
and Cumulative Update (CU) you want to upgrade to during the upgrade of the SQL Server. For the
Cumulative Update package, the initial download is a _zip.exe file. Make sure that you unzip the
package and copy the executable .exe to the Update Source directory.
Note
You can upgrade your SQL Server database either with the Service Pack and Cumulative Update as the
minimum required build (SP and CU) as specified in SAP Note 62988 , or with the latest Service Pack
and currently released Cumulative Update for the SQL Server product you want to upgrade. For more
information on how to set up the UpdateSource directory, see http://msdn.microsoft.com/en-us/
library/ms144259.aspx
.
6. Enter the required information as specified in the table below.
Note
The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL Server
\130\Setup Bootstrap\LOG\<YYYYMMDD_HHMM>. You can find the summary of the setup log in
Summary.txt in the same directory.
Table 5: Input for the SQL Server 2016 Upgrade on the First Cluster Node
Window
SQL Server Installation Center
Input
1.
Choose Installation.
2. Select Upgrade from a previous version of SQL Server.
Note
This window does not appear, if you run setup.exe
with the parameter /UpdateSource.
Setup Support Rules
If there are no failed operations or warnings, choose OK.
Otherwise, first check the failed operations and warnings.
Product Key
If this screen appears, enter the product key and choose
Next.
License Terms
Accept the Microsoft software license terms and choose
Next.
Global Rules
Check the global rule errors and warnings.
If there are no errors, the setup automatically advances to
the next window.
Microsoft Update
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
Select the check-box and choose Next.
PUBLIC
15
Window
Input
Product Updates
Displays the latest SQL Server updates, if available.
If there are no updates, the setup skips this screen.
Install Setup Files
The setup installs the setup files and product updates if
selected.
Upgrade Rules
Check the upgrade rule errors and warnings.
If there are no upgrade rule errors, the setup automati­
cally advances to the Select Instance window.
Select Instance
Select the SQL Server instance you want to upgrade and
then choose Next.
Select Features
Choose Next.
You cannot change the SQL Server features to be up­
graded.
Instance Configuration
Specify the instance ID for the instance of SQL Server.
By default, the instance name is used as the instance ID.
Choose Next.
Server Configuration
Full-Text Upgrade
Leave the default values unchanged and choose Next.
Select your option (see SQL Server Books Online for addi­
tional information) and choose Next.
Feature Rules
Check the failed feature rules and warnings.
If there are no feature rule errors, the setup automatically
advances to the Cluster Upgrade Report window.
Cluster Upgrade Report
Displays the upgrade status of the failover cluster nodes
Ready to Upgrade
Check the summary list and choose Upgrade.
Upgrade Progress
Displays the upgrade progress while adding the node to
the selected failover cluster.
Cluster Upgrade Report
Displays the upgrade status of the failover cluster nodes
after the upgrade
Complete
After the upgrade has been completed, the setup displays
the status and a link to the log files…
Choose Close to finish the installation.
7. Make sure that the upgraded node is one of the possible owners of the SQL Server applications or roles.
To check this property, perform the following steps:
1. In the Failover Cluster Manager, select the Roles node.
16
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
2. Select SQL Server or SQL Server (Instance).
3. In the right-hand bottom window, right-click the resource in the Server Name field and choose
Properties.
4. Choose the Advanced Policies tab and check that the upgraded node is on the list of possible owners.
If not, check the box for the possible owners and choose OK.
8. In the Failover Cluster Manager, move the SQL Server to the upgraded node.
After the SQL Server is moved successfully to the upgraded node, complete the upgrade on the second
node.
Start the installation program with one of the following:
○ setup.exe
(if you want to upgrade to the SQL Server RTM build)
You also get the option to install the latest Service Pack (SP) and Cumulative Update (CU) via the
Windows update service.
○ setup.exe /Action=Upgrade /UpdateSource="<Drive>:\<Upgrade_Source_Directory>"
where <Upgrade_Source_Directory> is the directory where you can copy the Service Pack (SP)
and Cumulative Update (CU) you want to upgrade to during the upgrade of the SQL Server. For the
Cumulative Update package, the initial download is a _zip.exe file. Make sure that you unzip the
package and copy the executable .exe to the Update Source directory.
Note
You can upgrade your SQL Server database either with the Service Pack and Cumulative Update as the
minimum required build (SP and CU) as specified in SAP Note 62988 , or with the latest Service Pack
and currently released Cumulative Update for the SQL Server product you want to upgrade. For more
information on how to set up the UpdateSource directory, see http://msdn.microsoft.com/en-us/
library/ms144259.aspx
.
Note
○ Make sure that you have installed or checked on the other node(s) all the prerequisites described
above.
○ Make sure that you upgrade your SQL Server to the same SQL Server build on both nodes.
Table 6: Input for the SQL Server 2016 Upgrade on the Second Cluster Node
Window
SQL Server Installation Center
Input
1.
Choose Installation.
2. Select Upgrade from a previous version of SQL Server.
Note
This window does not appear, if you run setup.exe
with the parameter /UpdateSource.
Setup Support Rules
If there are no failed operations or warnings, choose OK.
Otherwise, first check the failed operations and warnings.
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
PUBLIC
17
Window
Product Key
Input
If this window appears, enter the product key and choose
Next.
License Terms
Accept the Microsoft software license terms and choose
Next.
Global Rules
Check the global rule errors and warnings.
If there are no errors, the setup the setup automatically
advances to the Microsoft Update window.
Microsoft Update
Select the check-box and choose Next.
Product Updates
Displays the latest SQL Server updates, if available.
If there are no updates, the setup automatically advances
to Install Setup Files window.
Install Setup Files
The setup installs the setup files and product updates if
selected.
Upgrade Rules
Check the upgrade rule errors and warnings.
If there are no upgrade rule errors, the setup automati­
cally advances to the Select Instance window.
Select Instance
Select the SQL Server instance you want to upgrade and
choose Next.
Select Features
Choose Next.
You cannot change the SQL Server features to be up­
graded.
Instance Configuration
Specify the instance ID for the instance of SQL Server.
By default, the instance name is used as the instance ID.
Choose Next.
Server Configuration
Full-Text Upgrade
Leave the default values unchanged and choose Next.
Select your option (see SQL Server Books Online for addi­
tional information) and choose Next.
Feature Rules
Check the feature rule errors and warnings.
If there are no feature rule errors, the setup automatically
advances to the Cluster Upgrade Report window.
18
Cluster Upgrade Report
Displays the upgrade status of the failover cluster nodes
Ready to Upgrade
Check the summary list and choose Upgrade.
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
Window
Upgrade Progress
Input
Displays the upgrade progress while adding the node to
the selected failover cluster.
Cluster Upgrade Report
Displays the upgrade status of the failover cluster nodes
after the upgrade
Complete
After the upgrade has been completed, the setup displays
the status and a link to the log files…
Choose Close to finish the installation.
9. If the latest Service Pack and the Cumulative Update are not installed during the initial upgrade, install
them after the upgrade as described below.
For more information about the minimum required build, see SAP Note 62988 .
Perform the following steps to install the SQL Server updates:
1. Install the Service Pack and Cumulative Update on the passive node.
2. Move the SQL Server group to the second node that was updated.
3. Verify that all SQL Server resources are online on the currently active node.
4. Install the Service Pack and Cumulative Update on the passive node.
10. Run the SAP tools for MS SQL Server.
The SAP tools for MS SQL Server perform the post-upgrade steps that are required for all SAP products
based on SAP NetWeaver running on SQL Server 2016.
For more information about how to use and where to download them, see SAP Note 683447 .
11. Start the SAP system.
12. Connect with a database administrator logon to the SQL Server 2016 Management Studio and execute the
following commands:
use <SID> – where <SID> is your SAP database
go
EXEC sp_updatestats
go
It takes some time to replace the old SQL Server index statistics with new SQL Server 2016 statistics. You
can execute this while the SAP system is online.
13. Change the page verify option with the following commands:
use master
go
alter database <SID> SET PAGE_VERIFY CHECKSUM;
go
14. Test the failover of the SQL Server group between the cluster nodes.
Test the connection to the failover cluster from a SQL Server Management Studio query window installed
on a server (which is not part of the cluster) after moving the SQL Server group between the nodes.
15. Set the configuration for the SQL Server Agent [page 33].
16. If your system landscape is distributed and SAP application instances are installed on hosts other than the
database instance host, you need to install the SQL Server 2016 client software on these hosts as
described in Installing the SQL Server 2016 Client Software Manually [page 32].
17. When you have finished the upgrade, check that the TCP/IP protocol in the SQL Server Configuration
Manager is enabled.
Search for the SQL Server 2016 Configuration Manager application to enable TCP/IP.
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
PUBLIC
19
18. Download and install the SQL Server Mangement Tools by selecting the option Install SQL Server
Management Tools in the SQL Server Installation center.
In SQL Server 2016, SQL Server Management Tools is a separate installation option. The installation of SQL
Server Management studio is a SAP support requirement. You can install the SQL Server Management
Studio in one of the cluster nodes or in another windows server. Use the SQL Server Management Studio
and test the connection to the SQL Server failover cluster installed on the cluster nodes.
20
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Upgrading SQL Server to SQL Server 2016 for an Existing SAP System
5
Installing SQL Server 2016 for a New SAP
System
5.1
Introduction
The following sections describe how to install the SQL Server 2016 database software for a new SAP system.
The SQL Server software has to be installed on each host in the system where you intend to set up an SAP
instance. Depending on the type of host involved, you either have to install the software for the database server
or client.
5.2
Installing the SQL Server Database Software
Automatically with SQL4SAP
For more information about the installation of SQL Server 2016 with SQL4SAP, see SAP Note 2313067 . You
find the SQL4SAP.BAT script on the SQL Server 2016 RDBMS medium, as well as the tool documentation
SQL4SAP_docu.pdf.
5.3
Installing the SQL Server 2016 Database Server
Software Manually
Use
You have to install the SQL Server 2016 database server software on the database host.
Prerequisites
Before you install SQL Server 2016, make sure that that you have installed or updated all the required
prerequisites as described above.
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
PUBLIC
21
Procedure
1. Log on as a user who is a member of the local Administrators group.
2. Insert the SQL Server 2016 RDBMS medium in your media drive or copy it locally.
3. Change to the directory x64\EnterpriseEdition on the RDBMS DVD.
If you use the SQL Server RDBMS medium (for runtime customers), the SQL Server Setup is located in the
subdirectory x64\EnterpriseEdition. If you did not purchase your license from SAP, use the official
Microsoft SQL Server medium to start setup.exe.
4. Start the installation program with one of the following:
○ setup.exe
(if you want to install the SQL Server RTM build)
You also get the option to install the latest Service Pack (SP) and Cumulative Update (CU) via the
Windows update service.
○ setup.exe /Action=Install /UpdateSource="<Drive>:\<Upgrade_Source_Directory>"
where <Upgrade_Source_Directory> is the directory where you can copy the Service Pack (SP)
and Cumulative Update (CU) you want to install during the setup of the SQL Server. For the Cumulative
Update package, the initial download is a _zip.exe file. Make sure that you unzip the package and
copy the executable .exe to the Update Source directory.
Note
You can install your SQL Server database either with the Service Pack and Cumulative Update as the
minimum required build (SP and CU) as specified in SAP Note 62988 , or with the latest Service Pack
and currently released Cumulative Update for the SQL Server product you want to install. For more
information on how to set up the UpdateSource directory, see http://msdn.microsoft.com/en-us/
library/ms144259.aspx
.
5. Enter the required information as specified in the table below.
Note
The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL Server
\130\Setup Bootstrap\LOG\<YYYYMMDD_HHMM>. You find the summary of the setup log in
Summary.txt in the same directory.
Table 7: Input for the MS SQL Server 2016 Installation
Window
SQL Server Installation Center
Input
1.
Choose Installation.
2. Select New SQL Server Standalone installation or add features to an
existing installation.
Note
This window does not appear, if you run setup.exe with the parameter /
UpdateSource.
22
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
Window
Input
Product Key
If this window appears, enter the product key and choose Next.
License Terms
Accept the Microsoft software license terms and choose Next.
Global Rules
Check the global rule errors and warnings.
If there are no errors, the setup automatically advances to the Microsoft
Update window.
Microsoft Update
Select the check-box and choose Next.
Product Updates
Displays the latest SQL Server updates, if available.
If there are no updates, the setup skips this screen.
Install Setup Files
The setup installs the setup files and product updates if selected.
Install Rules
Check the install rule errors and warnings
If there are no install rule errors, the setup skips this screen.
Feature Selection
1.
Select the following features:
○
Database Engine Services
○
Full Text and Semantic Extractions for Search
○
Client Tools Connectivity
○
Client Tools Backward Compatibility
○
Client Tools SDK
○
Documentation Components
○
SQL Client Connectivity SDK
For shared feature directory and shared feature directory (x86), leave the
default value paths
The path specified for the shared components must be an absolute path.
The folder must not be compressed or encrypted. Mapped drives are also
not supported.
2. Choose Next.
Feature Rules
Setup checks the system state of your computer. If there are no failed opera­
tions or warnings, choose Next. Otherwise, check the failed operations and
warnings.
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
PUBLIC
23
Window
Instance Configuration
Input
1.
Specify the instance name and ID you want to install.
Since the configuration of SQL Server is easier to handle, we recommend
that you install a Default instance.
If you want to install a Named instance, enter the <SAPSID> in the Named
instance field.
2. Leave the Instance ID and Instance root directory field to the default val­
ues.
3. Choose Next.
Note
The Installed Instances grid shows the instances of SQL server that are
installed on the computer.
Server Configuration
1.
For the SQL Server Agent and SQL Server Database Engine services, en­
ter the Local system account in the Account Name column.
1.
For the English Windows version, the user name starts with NT
Authority, for example NT Authority\System.
2. Set the Startup Type for the SQL Server Agent to Automatic.
2. In the Collation tab, for the Database Engine, set the collation to
SQL_Latin1_General_CP850_BIN2.
To change the collation, use the Customize field.
3. Check the box to Grant Perform Volume Maintenance Task Privilege to SQL
Server Database Engine Service
4. When you have made all entries, choose Next.
Database Engine Configuration
1.
In the Server Configuration tab, select one of the following authentication
modes:
○
Windows Authentication Mode
We recommend that you use this mode for an ABAP system. With
this mode the sa login is created, but cannot be used.
○
Mixed Mode (Windows authentication and SQL Server authentication)
This mode is required for a Java or ABAP+Java system.
If you select this mode, you have to set the password for the sa login.
SAPinst automatically changes the authentication mode into Mixed
Mode when installing a Java system.
2. If you use Mixed Mode, enter and confirm the password for the built-in
SQL Server system administrator account.
The password for the sa login must comply with the Windows password
policy.
3. To specify an SQL Server administrator, choose Add
In the Select Users or Groups window, choose one Windows account as lo­
cal system administrator.
SAP strongly recommends that you enter Administrators in the Select
Users or Groups window.
4. Choose Next.
24
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
Window
Input
Feature Configuration Rules
If there are no failed operations or warnings, choose Next. Otherwise, first
check the failed operations and warnings.
Ready to Install
Check the summary list and select Install.
Installation Progress
Displays the installation progress.
Complete
After the installation has been completed, the setup displays the status and a
link to the log files.
choose Close to finish the installation.
6. Restart SQL Server.
7. If the latest Service Pack and Cumulative Update are not installed during the initial setup, install them after
the setup has finished. For more information about the minimum required build, see SAP Note 62988 .
8. Download and install the SQL Server Mangement Tools by selecting the option Install SQL Server
Management Tools in the SQL Server Installation center.
In SQL Server 2016, SQL Server Management Tools is a separate installation option. The installation of SQL
Server Management studio is a SAP support requirement.
9. Set the configuration for the SQL Server Agent [page 33].
5.4
Installing the SQL Server 2016 Failover Cluster
Use
This section describes how to install the SQL Server 2016 database server software for a high-availability
system with Microsoft failover clustering.
The SQL Server 2016 database server software must be installed on the database host.
Note
The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL Server
\130\Setup Bootstrap\LOG\<YYYYMMDD_HHMM>. You can find the summary of the setup log in
Summary.txt in the same directory.
To install the client software for an application server, see Installing the SQL Server 2016 Client Software
Manually [page 32].
Prerequisites
Before you install SQL Server 2016, make sure that you have installed or updated all the required prerequisites
as described above.
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
PUBLIC
25
Procedure
1. Log on all cluster nodes as a domain user who is a member of the local administrators group with the
permissions to log on as a service and to act as part of the operating system.
2. Move all the cluster resources and groups to the first cluster node.
3. Insert the SQL Server 2016 RDBMS medium in your media drive or copy it locally.
4. Change to the directory:
x64\EnterpriseEdition.
If you use the SQL Server RDBMS medium (for runtime customers), the SQL Server Setup is located in the
subdirectory x64\EnterpriseEdition. If you did not purchase your license from SAP, use the official
Microsoft SQL Server medium to start setup.exe.
5. Start the installation program on the first cluster node with one of the following:
○ setup.exe
(if you want to install the SQL Server RTM build)
You also get the option to install the latest Service Pack (SP) and Cumulative Update (CU) via the
Windows update service.
○ setup.exe /Action=Installfailovercluster/UpdateSource=<Drive>:
\<Upgrade_Source_Directory>"
where <Upgrade_Source_Directory> is the directory where you can copy the Service Pack (SP)
and Cumulative Update (CU) you want to install during the setup of the SQL Server. For the Cumulative
Update package, the initial download is a _zip.exe file. Make sure that you unzip the package and
copy the executable .exe to the Update Source directory.
Note
You can install your SQL Server database either with the Service Pack and Cumulative Update as the
minimum required build (SP and CU) as specified in SAP Note 62988 , or with the latest Service Pack
and currently released Cumulative Update for the SQL Server product you want to install. For more
information on how to set up the UpdateSource directory, see http://msdn.microsoft.com/en-us/
library/ms144259.aspx
.
6. Enter the required information as specified in the table below.
Table 8: Input for the SQL Server 2016 Installation on the First Cluster Node
Window
SQL Server Installation Center
Input
1.
Choose Installation.
2. Select New SQL Server failover cluster installation.
Note
This window does not appear, if you run setup.exe with the parameter /
UpdateSource.
26
Product Key
If this window appears, enter the product key and choose Next.
License Terms
Accept the Microsoft software license terms and choose Next.
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
Window
Input
Global Rules
Check the global errors and warnings.
If there are no errors, the setup automatically advances to the Microsoft
Update window.
Microsoft Update
Select the check-box and choose Next.
Product Updates
Displays the latest available SQL Server updates, if available.
The setup downloads the product updates.
Install Setup Files
The setup installs the setup files and product updates if selected.
Install Failover Cluster Rules
If there are no failed operations or warnings, choose Next.
Otherwise, first check the failed operations or warnings.
Feature Selection
1.
Select the following features:
○
Database Engine Services
○
SQL Server Replication
○
Full Text and Semantic Extractions for Search
○
Data Quality Services
○
Client Tools Connectivity
○
Client Tools Backwards Compatibility
○
Client Tools SDK
○
Documentation Components
○
SQL Client Connectivity SDK
Note
In a failover cluster installation, the features SQL Server Replication,
Full Text and Semantic Extractions for Search and Data Quality Services
are mandatory and you cannot deselect them.
For shared feature directory and shared feature directory (x86), leave
the default value paths
The path specified for the shared components must be an absolute
path. The folder must not be compressed or encrypted. Mapped drives
are also not supported.
2. Choose Next.
Feature Rules
SQL Server setup runs setup rules based on the features you selected to vali­
date your configuration.
If there are no feature rule errors or warnings, the setup automatically advan­
ces to the next window. Otherwise, check the failed rules and warnings.
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
PUBLIC
27
Window
Instance Configuration
Input
1.
Enter the SQL Server network name.
2. Select the instance type you want to install.
Since the configuration of SQL Server is easier to handle, we recommend
that you install a Default instance.
If you want to install a Named instance, enter the <SAPSID> in the Named
instance field.
3. Leave the default values Instance ID and Instance root directory field to the
default values.
4. Choose Next.
Cluster Resource Group
Cluster Disk Selection
Specify the SQL Server cluster resource group and choose Next.
1.
Specify the shared disk to be included in the SQL Server resource cluster
group.
2. Choose Next.
Cluster Network Configuration
1.
Specify the IP type and address.
2. If you do not have DHCP addresses, enter a static IP address and subnet
mask
3. Choose Next.
Server Configuration
1.
In the Service Accounts tab, for the SQL Server Agent and SQL Server Da­
tabase Engine services, enter the domain accounts (part of the adminis­
trator group of the cluster nodes) in the Account name column, and the
password in the Password column.
2. In the Collation tab, for the Database Engine, set the collation to
SQL_Latin1_General_CP850_BIN2.
To change the collation, use the Customize field.
3. Check the box to Grant Perform Volume Maintenance Task Privilege to SQL
Server Database Engine Service.
4. When you have made all entries, choose Next.
28
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
Window
Database Engine Configuration
Input
1.
In the Server Configuration tab, select one of the following authentication
modes:
○
Windows Authentication Mode
We recommend that you use this mode for an ABAP system. With
this mode the sa login is created, but cannot be used.
○
Mixed Mode (Windows authentication and SQL Server authentication)
This mode is required for a Java or ABAP+Java system.
If you select this mode, you have to set the password for the sa login.
The installer automatically changes the authentication mode into
Mixed Mode when installing a Java system.
2. If you use Mixed Mode, enter and confirm the password for the built-in
SQL Server system administrator account.
The password for the sa login must comply with the Windows password
policy.
3. To specify an SQL Server administrator, choose Add.
In the Select Users or Groups window, choose one Windows account as lo­
cal system administrator.
SAP strongly recommends that you enter Administrators in the Select
Users or Groups window.
4. Choose Next.
Feature Configuration Rules
If there are no failed operations or warnings, choose Next. Otherwise, first
check the failed operations and warnings.
Ready to Install
Check the summary list and select Install.
Installation Progress
Displays the installation progress.
Complete
After the installation has been completed, the setup displays the status and a
link to the log files.
choose Close to finish the installation.
7. When you have finished installing the SQL Server failover cluster on the first cluster node, complete the
cluster installation by restarting the installation program on the second cluster node.
Start the installation program with one of the following:
○ setup.exe
(if you want to install the SQL Server RTM build)
You also get the option to install the latest Service Pack (SP) and Cumulative Update (CU) via the
Windows update service.
○ setup.exe /Action=Addnode /UpdateSource="<Drive>:\<Upgrade_Source_Directory>"
where <Upgrade_Source_Directory> is the directory where you can copy the Service Pack (SP)
and Cumulative Update (CU) you want to install during the setup of the SQL Server. For the Cumulative
Update package, the initial download is a _zip.exe file. Make sure that you unzip the package and
copy the executable .exe to the Update Source directory.
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
PUBLIC
29
Note
You can install your SQL Server database either with the Service Pack and Cumulative Update as the
minimum required build (SP and CU) as specified in SAP Note 62988 , or with the latest Service Pack
and currently released Cumulative Update for the SQL Server product you want to install. For more
information on how to set up the UpdateSource directory, see http://msdn.microsoft.com/en-us/
library/ms144259.aspx
.
Note
Make sure you install the SQL Server database with the same build in both nodes.
8. Enter the required information as specified in the table below.
Table 9: Input for the SQL Server 2016 Cluster Installation Completion on the Second Cluster Node
Window
SQL Server Installation Center
Input
1.
Choose Installation.
2. Select Add node to a SQL Server failover cluster cluster.
Note
This window does not appear, if you run setup.exe with the parameter /
UpdateSource.
Product Key
If this window appears, enter the product key and choose Next.
License Terms
Accept the Microsoft software license terms and choose Next.
Global Rules
Check the global rule errors and warnings.
If there are no errors, the setup automatically advances to the Microsoft
Update window.
Microsoft Update
Select the check-box and choose Next.
Product Updates
Displays the latest available SQL Server updates, if available.
The setup downloads the product updates.
Install Setup Files
The setup installs the setup files and product updates if selected.
Add Node Rules
If there are no failed operations or warnings, choose Next.
Otherwise, first check the failed operations or warnings.
Cluster Node Configuration
Select the instance name and choose Next.
Cluster Network Configuration
Check the values and choose Next.
Service Accounts
Enter the password for the SQL Server and SQL Agent Services accounts and
choose Next.
30
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
Window
Input
Feature Rules
The system configuration checker runs one or more set of rules to validate
your system configuration based on the selected features.
If there are no feature rule errors or warnings, the setup skips this screen. Oth­
erwise, check the failed rules and warnings.
Ready to Add Node
Displays the selected options to add the node to the failover cluster.
Check the options and select Install.
Add Node Progress
Displays the installation progress of the selected features when adding the
node to the failover cluster.
Complete
After the installation has been completed, the setup displays the status and a
link to the log files.
Choose Close to finish the installation.
9. Restart SQL Server.
10. Download and install the SQL Server Mangement Tools by selecting the option Install SQL Server
Management Tools in the SQL Server Installation center.
In SQL Server 2016, SQL Server Management Tools is a separate installation option. The installation of SQL
Server Management studio is a SAP support requirement. You can install the SQL Server Management
Studio in one of the cluster nodes or in another windows server. Use the SQL Server Management Studio
and test the connection to the SQL Server failover cluster installed on the cluster nodes.
11. After the SQL Server 2016 failover installation has finished successfully on the second cluster node, make
sure that you can fail over the SQL Server group between the nodes.
Test the connection to the failover cluster from a SQL Server Management Studio query window installed
on a server (which is not part of the cluster) after moving the SQL Server group between the nodes.
12. If the latest Service Pack and the Cumulative Update are not installed during the initial setup, install them
after the setup has finished on both the nodes as described below.
For more information about the required Service Pack and Cumulative Update, see SAP Note 62988 .
Perform the following steps to install the SQL Server updates:
1. Install the Service Pack and Cumulative Update on the passive node.
2. Move the SQL Server group to the second node that was updated.
3. Verify that all SQL Server resources are online on the currently active node.
4. Install the Service Pack and Cumulative Update on the passive node.
13. Test the failover of the SQL Server group between the cluster nodes.
14. After the installation of SQL Server Failover cluster, you need to add dependencies for SQL Server on the
shared disks that will be used to store SAP database files.
To do so, perform the following steps:
1. In the Failover Cluster Manager, select the Roles node.
2. Right-click on the SQL Server (MSSQLSERVER) or SQL Server (<NamedInstance>) role, and then
select Add Storage.
3. In the Add Storage pop-up window, select the disks you want to move to the SQL Server
(MSSQLSERVER) or SQL Server(<NamedInstance>) role, and choose OK.
4. Make sure you can see all the resources for the SQL Server (MSSQLSERVER) or SQL
Server(<NamedInstance>) role node in the bottom window.
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
PUBLIC
31
If not, click on the resources tab in the bottom window, so you can see all resources.
5. In the resources tab in the bottom window, right-click the SQL Server or SQL Server
(<NamedInstance>) resource and take the SQL Server or SQL Server (<NamedInstance>) resource
offline. This action will also take the dependency resource SQL Server Agent or SQL Server Agent
(<NamedInstance>) offline.
6. Right-click the SQL Server or SQL Server(<NamedInstance>) resource and select Properties.
7. In the Dependencies window, add the previously shared disks by using the AND operator in the field
click here to add a dependency and click Insert.
8. Bring the SQL Server or SQL Server (<NamedInstance>) and SQL Server Agent or SQL Server Agent
(<NamedInstance>) resources online.
15. Set the configuration for the SQL Server Agent [page 33].
5.5
Installing the SQL Server 2016 Client Software
Manually
Use
This section describes how to install the SQL Server 2016 client software.
You have to install the SQL Server 2016 client software on all SAP application servers. It enables the
communication between an application server and the database.
If there are updates to the client software in either a Service Pack (SP) or a Cumulative Update (CU), the SP or
CU needs to be running on each application server to make sure that the client software changes are applied
consistently to the database server and to the application server.
Procedure
1. Log on as local administrator to the host where you want to install an application server.
2. Insert the SQL Server 2016 RDBMS (for runtime customers) or the SQL Server 2016 RDBMS (for nonruntime customers) medium in your media drive or copy it locally.
3. Change to the directory <RDBMS_Medium>:\SqlNativeClient\<Platform>\ and double-click the
msodbcsql.msi installer.
For more information, see SAP Note 2313067
.
4. Follow the instructions in the SQL Server installation setup screens.
32
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Installing SQL Server 2016 for a New SAP System
6
Setting the SQL Server Agent
Configuration
Use
After you have installed or upgraded to SQL Server 2016, you must set the configuration for the SQL Server
Agent.
Procedure
1. Start the SQL Server Management Studio.
2. Right-click SQL Server Agent and choose Properties.
3. Choose History.
4. Set the value for column Maximum job history log size (in rows) to 6000 (minimum).
5. Set the value for column Maximum job history rows per job to 500 (minimum).
6. Check the column Remove agent history and set a value for this column.
7. To save the settings, choose OK.
Note
If multiple SAP systems are installed in the same SQL Server, configure the SQL Agent log history size as
described in SAP note 1730470 .
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Setting the SQL Server Agent Configuration
PUBLIC
33
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as
"sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun
does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any
damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for
transparency (see: https://help.sap.com/viewer/disclaimer).
34
PUBLIC
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Important Disclaimers and Legal Information
Upgrade to and Installation of SQL Server 2016 in an SAP Environment
Important Disclaimers and Legal Information
PUBLIC
35
go.sap.com/registration/
contact.html
© 2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see https://www.sap.com/corporate/en/legal/copyright.html
for additional trademark information and notices.