Sql2008r2 Upgrade v150

Upgrade and Installation GuideUpgrade to and Installation of SQL Server 2008 (R2) in an SAP Environment

Target Audience ■ Technology Consultants ■ System Administrators

CUSTOMERDocument version: 1.50 – 2013-06-14

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2/38 CUSTOMER 2013-06-14

http://www.sap.com

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0


Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version at the following location:

http://service.sap.com/instguides

Version Date Description

1.50 2013-06-14 Updated VersionAdditional information about SNAC client added

1.40 2012-10-29 Updated Version ■ Section Clustering the SQL Server 2008 (R2) Database Server Software:

Changes in 1st step of Procedure, and in table Input for the MS SQL Server 2008 (R2) Installation on the First Cluster Node, column Server Configuration.

■ Sections Upgrading SQL Server to SQL Server 2008 (R2) for an Existing Non-High-Availability SAP System and Upgrading SQL Server to SQL Server 2008 (R2) for an Existing High-Availability SAP System:New location for SAP tools for MS SQL Server (SAP note 683447)

1.30 2012-06-15 Updated VersionSection Setting the SQL Server Agent Configuration:Changed values for maximum job history log size, and maximum job history rows per job

1.20 2011-11-30 Updated VersionSAP notes updated in section General Requirements and Restrictions

1.10 2011-04-11 Updated VersionProcedure for changing page verify option added in sections: ■ Upgrading SQL Server to SQL Server 2008 (R2) for an Existing Non-High-Availability SAP

System

■ Upgrading SQL Server to SQL Server 2008 (R2) for an Existing SAP High-Availability System.

1.00 2010-09-20 Initial Version

2013-06-14 CUSTOMER 3/38


Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 General Requirements and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3 Upgrading SQL Server to SQL Server 2008 (R2) for an Existing SAP

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1 General Prerequisites for Upgrading SQL Server to SQL Server 2008

(R2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.2 Upgrading SQL Server to SQL Server 2008 (R2) for an Existing Non-High-

Availability SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.3 Upgrading SQL Server to SQL Server 2008 (R2) for an Existing High-

Availability SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 4 Installing SQL Server 2008 (R2) for a New SAP System . . . . . . . . . . . . . . . . 23

4.1 Installing the SQL Server Database Software Automatically with

SQL4SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.2 Installing the SQL Server 2008 (R2) Database Server Software

Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.3 Clustering the SQL Server 2008 (R2) Database Server Software . . . . . . . . . . . . 27

4.4 Installing the SQL Server 2008 (R2) Native Client Software

Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 5 Setting the SQL Server Agent Configuration . . . . . . . . . . . . . . . . . . . . . . . 35

4/38 CUSTOMER 2013-06-14

1 Introduction

This document describes the upgrade to or installation of SQL Server 2008 (R2) for an SAP system.

You have the following options to use SQL Server 2008 (R2) in an SAP environment:

■ You upgrade an existing SQL Server 2000 or SQL Server 2005 instance that is already running an

SAP system to SQL Server 2008 (R2). SAP does not support any upgrade method other than that

described here. For more information, see Upgrading SQL Server to SQL Server 2008 (R2) for an Existing

SAP System [page 11].

CAUTION

Before you upgrade SQL Server 2000 or SQL Server 2005 to SQL Server 2008 (R2), make sure

that you import the required support packages [page 7] to your system. Otherwise, the

upgraded system does not function correctly with SQL Server 2008 (R2).

■ You upgrade an existing SQL Server 2008 instance that is already running an SAP system to SQL

Server 2008 R2. Since SQL Server 2008 R2 is treated as a Service Pack for SQL Server 2008, prepare

your landscape as you would do for an upgrade to SQL Server 2008.

■ You install SQL Server 2008 (R2) for a new SAP system that is based on SAP NetWeaver 7.0 SR3,

SAP NetWeaver 7.0 EHP1 SR1 (7.01 SR1) or SAP NetWeaver 7.1, and higher. For more information,

see Installing SQL Server 2008 (R2) for a New SAP System [page 23].

NOTE

If you want to install SQL Server 2008 (R2) for an SAP system that is based on SAP NetWeaver

7.1, see SAP Note 1152240.

You have the following options to install SQL Server 2008 (R2) for a new SAP system.

● You install SQL Server 2008 (R2) for a non-high-availability (non-HA) SAP system

You can either install the SQL Server database software using a special VB script named

SQL4SAP.vbs provided by SAP, or you can install it manually.

NOTE

We highly recommend that you perform any new installation of an SQL Server 2008 (R2)

instance for a non-HA system with the SQL4SAP.vbs script. The script is located on the

SQL Server 2008 (R2) RDBMS DVD that is shipped with the SAP products.

● You install SQL Server 2008 (R2) for a high availability (HA) SAP system

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.VBS script.

1 Introduction

2013-06-14 CUSTOMER 5/38


■ You perform a system copy of an SAP system based on SAP NetWeaver 7.0 SR3, SAP NetWeaver 7.0

EHP1 SR1 (7.01 SR1), or SAP NetWeaver 7.1, and higher. For more information, see SAP Note

1152240.

1 Introduction

6/38 CUSTOMER 2013-06-14


2 General Requirements and Restrictions

Required SAP Notes

Read the following SAP notes before using SQL Server 2008 (R2):

General SAP Notes

Note Number Title Remarks

1152240 Setting Up Microsoft SQL Server 2008 (R2)

Provides the latest information about the upgrade to and installation of SQL Server 2008 (R2).

1076022 Release planning for Microsoft SQL Server 2008 (R2)

Provides release planning information about SQL Server 2008 and SQL Server 2008 R2, including the minimum SAP support package levels

1252970 Triggers on SAP tables In general, SAP does not support any triggers on SAP tables in SQL Server. If, due to application-specific requirements, you have to use triggers on SAP tables in SQL Server, follow the guidelines stated in this SAP note.

1581700 PAGE compression support for DDIC & Hom./Het. System Copy

Provides SQL Server PAGE compression support for tables and indexes during a homogenous or heterogeneous system copy using the R3Load method

1488135 Database compression for SQL Server

Describes how to implement ROW and PAGE compression for SQL Server 2008 (and higher) for SAP products based on SAP Application Server ABAP

SAP Business Warehouse (SAP BW)-Specific SAP Notes

Note Number Title Remarks

1654613 SQL Server Parallelism for SAP BW –

Required Support Packages

For more information about the minimum support package levels to run on SQL Server 2008 (R2) for

your SAP system, see SAP note 1076022.


2013-06-14 CUSTOMER 7/38








NOTE

We recommend that you apply all available basis support packages before using SQL Server 2008

(R2) in a production system.

General Requirements and Restrictions for Using SQL Server 2008 (R2)

Note the following general requirements and restrictions, which both apply when using SQL Server

2008 (R2) for a non-HA or a HA SAP system:

■ Only SAP releases based on SAP NetWeaver 7.0 SR3, SAP NetWeaver 7.0 EHP1 SR1, or SAP NetWeaver

7.1, and higher are supported to run on SQL Server 2008 (R2). For more information, see SAP Note

1152240.

■ Not all combinations of SQL Server 2008 (R2) and Windows are supported by all SAP products.

For up-to-date information on supported releases of SAP systems with SQL Server 2008 (R2), see

the Product Availability Matrix (PAM) at:

http://service.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.

■ Only the SQL Server 2008 (R2) 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 2008 (R2), make sure that you have enough free disk

space available on the system drive for:

● Net Framework

For 64-bit, in addition to the 32-bit .Net Framework, the 64-bit .Net Framework is also installed.

● 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 4 GB free disk space on the system

drive.

Additional Requirements and Restrictions for Using SQL Server 2008 (R2) 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 2008 (R2) in a high-availability (HA)

system.

NOTE

For a complete list of the restrictions and more information, see:

■ SQL Server 2008 Books Online at:


8/38 CUSTOMER 2013-06-14



http://msdn.microsoft.com/en-us/library/bb543165.aspx

■ SQL Server 2008 R2 Books Online at:

http://msdn.microsoft.com/en-us/library/ms130214.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.

■ Windows Server 2003: You have created domain user groups for each clustered service such as SQL

Server, SQL Agent, as follows:

● Ask the domain administrator to create the domain groups with the Group Type Security and

Group Scope Global

● The group names must already exist in the domain before starting the SQL Server upgrade.

● Ask your domain administrator to add the startup account for each service to the

corresponding domain group

● Microsoft recommends that you use a different domain group for each service.

● Microsoft recommends that you do not share the SQL Server domain groups with other

applications.


2013-06-14 CUSTOMER 9/38

http://msdn.microsoft.com/en-us/library/bb543165.aspx


http://support.microsoft.com/kb/250355/en-us

http://support.microsoft.com/kb/250355/en-us

This page is left blank for documents that are printed on both sides.

3 Upgrading SQL Server to SQL Server 2008 (R2) for an Existing SAP System

The following sections describe how to upgrade SQL Server 2000 or SQL Server 2005 to SQL Server 2008

(R2).

CAUTION

The upgrade procedure in this document is only valid if the SQL Server database 2000 or 2005

software was installed by the SAP script or manually as described in the SQL Server 2000 or SQL

Server 2005 Upgrade and Installation Guide.

3.1 General Prerequisites for Upgrading SQL Server to SQL Server 2008 (R2)

If you want to upgrade SQL Server 2000 or SQL Server 2005 for an existing SAP system, you must meet

the following prerequisites:

■ You use Windows Server 2003 SP2 or higher.

■ You use an SAP system based on SAP NetWeaver 7.0 SR3, SAP NetWeaver 7.0 EHP1 SR1, or SAP

NetWeaver 7.1, and higher with the minimum recommended support package level for SQL Server

2008 (R2).

■ You have imported the latest SAP kernel patches, dbsl library, and support packages, 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.

■ Only valid for: Java |

If you use a Java system, you have updated the JDBC driver as described in SAP Note 639702End of: Java |

■ If your SQL Server release is SQL Server 2005, make sure that you have applied SP2 to your system

before you upgrade your system to SQL Server 2008 (R2).

■ If you installed the SQL Server 2000 or SQL Server 2005 database software with the SQL4SAP.VBS

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.


3.1 General Prerequisites for Upgrading SQL Server to SQL Server 2008 (R2)

2013-06-14 CUSTOMER 11/38



■ You have backed up your SQL Server database.

■ You have shut down the SAP system.

3.2 Upgrading SQL Server to SQL Server 2008 (R2) for an Existing Non-High-Availability SAP System

This section provides information about the upgrade of SQL Server 2000 or SQL Server 2005 system to

SQL Server 2008 (R2) 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.

Therefore, we do not support upgrading a 32-bit SQL Server 2000 or SQL Server 2005 database

server to SQL Server 2008 (R2).

Prerequisites

■ You have met the general prerequisites [page 11].

■ If your SQL Server release is SQL Server 2000, make sure that you apply SP4 to the system before

you upgrade to SQL Server 2008 (R2).

■ Make sure that the server and database collations are set to SQL_Latin1_General_CP850_BIN2.

For more information on the collation for SQL Server 2000, see SAP Note 600027.

■ SQL Server 2008 (R2) requires Microsoft .NET Framework 3.5 (x64) or Microsoft .NET Framework 2.0 (IA64,

Windows Server 2003).

● Windows Server 2008 R2:

Add the .NET Framework 3.5 SP1 feature as follows:

1. Log on as local administrator.

2. Open an elevated command prompt.

3. Enter the following command:

servermanagercmd –install NET-Framework-Core

4. Reboot your system.

● Windows Server 2008 (or lower):

Install or update the Microsoft .Net Frameworks as follows:

1. Log on as a local administrator.

2. Insert the SQL Server 2008 RDBMS DVD or SQL Server 2008 R2 RDBMS DVD in your

DVD drive or copy it locally.

3. Run one of the following .Net Frameworks executables:

◆ For x64, run the executable dotNetFx35setup.exe, which is located in the following

directory:

▶ SQL Server 2008:

x86-x64-IA64\EnterpriseEdition\<platform>\redist\DotNetFrameworks



12/38 CUSTOMER 2013-06-14


▶ SQL Server 2008 R2:

x86-x64-IA64\EnterpriseEdition\redist\DotNetFrameworks\dotNetFX35

\<platform>

◆ For IA64, Windows Server 2003, run the executable NetFx20SP2_ia64.exe, which is

located in the directory:

x86-x64-IA64\EnterpriseEdition\ia64\redist\2.0

4. Accept the licensing terms for the .Net Frameworks and choose Install.

5. After the installation of the .Net Frameworks has finished, reboot your system.

Procedure

1. Upgrade the SQL Server 2000 or 2005 instance to SQL Server 2008 (R2) as follows:

1. Log on to the host as a local administrator.

2. Insert the SQL Server 2008 RDBMS DVD or SQL Server 2008 R2 RDBMS DVD for an upgrade

to SQL Server 2008 R2 in your DVD drive or copy it locally.

3. Change to the directory:

x86-x64-ia64\EnterpriseEdition.

4. Start the installation program with setup.exe.

NOTE

Make sure that you have installed or updated the Microsoft .Net Frameworks as described

under Prerequisites above.

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\100\Setup Bootstrap\LOG\<YYYYMMDD_HHMM>. You find the summary of the

setup log in Summary_<HOSTNAME><YYYYMMDD_HHMM>.txt in the same directory.

Window Input

Windows Update Standalone Installer If you have not installed the required Windows prerequisites, install them as follows:1. To install the Windows hotfix, choose OK.2. When the installation is finished, reboot your

system, if required.3. Restart the installation with setup.exe.

Installation Prerequisites Choose Install.Setup installs SQL Server support files.

SQL Server Installation Center 1. Choose Installation.2. Choose Upgrade from SQL Server 2000 or SQL Server

2005 or SQL Server 2008.

Setup Support Rules If there are no failed operations or warnings, choose OK. Otherwise, first check the warnings.

Product Key Enter the product key and choose Next.



2013-06-14 CUSTOMER 13/38

Window Input

License Terms Accept the Microsoft software license terms and choose Next.

Setup Support Files Choose Install.

Setup Support Rules If there are no failed operations or warnings, choose Next. Otherwise, first check the warnings.

Select Instance Select the instance you want to upgrade and choose Next.

Select Features Choose Next.

Instance Configurations Leave the default values and choose Next.

Disk Space Requirements Review the disk space requirements and choose Next.

Server Configuration If required, enter the service accounts and then choose Next.For more information, see SQL Server Books Online.

Full Text Upgrade Select your option (see SQL Server Books Online for additional information) and then choose Next.

Error and Usage Reporting Select the required usage reporting and choose Next.

Upgrade Rules If there are no failed operations or warnings, choose Next. Otherwise, first check the warnings.

Ready to Upgrade The setup validates the input and analyzes the upgrade.Review the status and then choose Upgrade.

Upgrade Progress The upgrade progress is shown with an indicator.When finished press Next.

Complete The setup writes a status screen and shows the location of the full upgrade log.

Completing Microsoft SQL Server 2008 Setup After the upgrade has been completed, choose Close.

6. When you have finished the upgrade, check that the Named Pipes and TCP/IP protocol in the

SQL Server Configuration Manager are enabled.

If required, enable them as follows:

1. Choose Start All Programs Microsoft SQL Server 2008 (R2) Configuration Tools SQL Server

Configuration Manager .

2. Expand SQL Server Network Configuration and select one of the following:

■ For a default instance, select Protocols for MSSQLServer

■ For a named instance, select Protocols for <SAPSID>

3. In the right-hand pane, under Protocol Name, right-click Named Pipes and TCP/IP, and select

Enable.

7. Restart SQL Server.



14/38 CUSTOMER 2013-06-14

8. Install the latest Service Pack and Cumulative Update. For more information, see SAP Note

62988.

9. If you require the SQL Server 2008 (R2) Management tools, which are not installed with the

upgrade of SQL Server 2000 (IA64) to SQL Server 2008 (R2), relaunch setup.exe and enter the

information as described in the following table:

Window Input

SQL Server Installation Center Choose the SQL Server standalone installation or add features to an existing installation.




Instance Type 1. Select Add features to an existing instance of SQL Server 2008 and select the instance.

2. Choose Next.

Feature Selection 1. Choose the required tools in the shared features.

NOTE

The Tools Integration Services and Microsoft Sync Framework are not required for SAP applications.

2. Choose Next.

Error and Usage Reporting Settings Select the required usage reporting and choose Next.

Installation Rules If there are no failed operations or warnings, choose Next. Otherwise, first check the warnings.

Ready to Install Check the summary list and choose Install.

Installation Progress You can monitor the installation progress of selected features in this screen.When finished, choose Next.

Complete Review the overview and log if necessary and choose Close.

2. Run the SAP tools for MS SQL Server.

The SAP tools for MS SQL Server perform the post-upgrade steps that are required for SAP ABAP

products running on SQL Server 2008 (R2). For more information about how to use and where to

download them, see SAP Note 683447.

3. Start the SAP system.

4. Connect with a database administrator logon to the SQL Server 2008 (R2) Management Studio and

execute the following commands:

use <SID> – where <SID> is your SAP database

go



2013-06-14 CUSTOMER 15/38



EXEC sp_updatestats

go

It takes some time to replace the old SQL Server index statistics with new SQL Server 2008 (R2)

statistics. You can execute this while the SAP system is online.

5. Change the page verify option with the following commands:

use master

go

alter database <SID> SET PAGE_VERIFY CHECKSUM;

go

6. Set the configuration for the SQL Server Agent [page 35].

7. 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 2008 R2 SNAC client on these

hosts as described in Installing the SQL Server 2008 (R2) Native Client Software Manually [page 32].

3.3 Upgrading SQL Server to SQL Server 2008 (R2) for an Existing High-Availability SAP System

This section provides information about the upgrade of SQL Server 2000 or SQL Server 2005 system to

SQL Server 2008 (R2) in an existing high-availability (HA) system.

CAUTION

You cannot upgrade the clustered SQL Server 2000 (IA64) to a clustered SQL Server 2008 (R2).

Instead you have to uninstall the existing SQL Server databases and install a new clustered SQL

Server 2008 (R2). When you have finished, follow the instructions for a homogeneous system

copy.

Prerequisites

■ You have met the general prerequisites [page 11].

■ 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

2008 (R2).

■ You review the following sections in SQL Server Books Online:

● Before Installing Failover Clustering

● Preinstallation Checklist

■ SQL Server 2008 (R2) requires Microsoft .NET Framework 3.5 (x64) or Microsoft .NET Framework 2.0 (IA64,

Windows Server 2003).

For more information, see http://msdn.microsoft.com/en-us/library/ms191295.aspx




16/38 CUSTOMER 2013-06-14













3. Run one of the following .Net Frameworks executables:

◆ For x64, run the executable dotNetFx35setup.exe, which is located in the following

directory:

▶ SQL Server 2008:


▶ SQL Server 2008 R2:


\<platform>

◆ For IA64, Windows Server 2003, run the executable NetFx20SP2_ia64.exe, which is

located in the directory:

x86-x64-IA64\EnterpriseEdition\ia64\redist\2.0


5. After the installation of the .Net Frameworks is finished, reboot your system.

■ You install the Microsoft Installer (MSI) 4.5 or higher, and the SQL Server support files:


x86-x64-IA64\Enterprise Edition

2. Start the installation program with setup.exe

3. Install the Microsoft Installer (MSI) 4.5 file and the support files.

■ Windows Server 2003 only:

If you use Windows Server 2003, request and download the Windows hotfix for your server

architecture at:

http://support.microsoft.com/kb/937444.

Install the hotfix on the current node.

■ You reboot the node.

■ You perform a failover to an upgraded node that meets all the prerequisites.

■ You install the Microsoft .Net Framework, Microsoft Installer. setup support files, and, the

Windows hotfix (Windows Server 2003) on the second node.



2013-06-14 CUSTOMER 17/38

http://support.microsoft.com/kb/937444

Procedure

After having met all prerequisites on all nodes, start the failover cluster upgrade of the SQL Server

instance to SQL Server 2008 (R2).

Perform the following steps on all cluster nodes, beginning with the passive node:

1. Log on to the host as a domain administrator user on all nodes.

2. Insert the SQL Server 2008 or SQL Server 2008 R2 RDBMS DVD in your DVD drive or copy it locally.

3. Move all the cluster resources and groups to the first cluster node.

4. Change to the directory x86-x64-IA64\EnterpriseEdition.

5. Start the installation program with setup.exe.

NOTE


under Prerequisites above.

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

\100\Setup Bootstrap\LOG\<YYYYMMDD_HHMM>. You can find the summary of the setup log

in Summary_<HOSTNAME><YYYYMMDD_HHMM>.txt in the same directory.

Window Input

Windows Update Standalone Installer If you have not yet installed the required Windows prerequisites, install them as follows:1. To install the Windows hotfix, choose OK2. Windows Server 2003:

Install hotfix KB937444.3. When the installation of the hotfix(es) is

finished, reboot your system.4. Restart the installation with setup.exe.

Installation Prerequisites Choose Install.If required, the SQL Server Setup installs SQL Server support files.

SQL Server Installation Center 1. Choose Installation.2. Choose Upgrade from SQL Server 2000 or SQL Server

2005.


Product Key Enter the product key and choose Next.







18/38 CUSTOMER 2013-06-14

Window Input

Select Features Choose Next.

Instance Configurations Leave the default values and choose Next.


Server Configuration If required, enter the service accounts and then choose Next.For more information, see SQL Server Books Online.

Full Text Upgrade Select your option (see SQL Server Books Online for additional information) and then choose Next.



Ready to Upgrade The setup validates the input and analyzes the upgrade.Review the status and then choose Upgrade.

Upgrade Progress The upgrade progress is shown with an indicator.When finished press Next.

Complete The setup writes a status screen and shows the location of the full upgrade log.

Completing Microsoft SQL Server 2008 Setup After the upgrade has been completed, choose Close.

7. When you have finished, complete the upgrade on the second cluster node:

NOTE

Make sure that you have installed or updated the Microsoft .Net Frameworks on the other

node(s) as described under Prerequisites above.

1. Restart the installation program with setup.exe on the second cluster node.


NOTE

The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL

Server\100\Setup Bootstrap\LOG\<YYYYMMDD_HHMM>. You can find the summary of

the setup log in Summary_<HOSTNAME><YYYYMMDD_HHMM>.txt in the same directory.

Window Input

Windows Update Standalone Installer If you have not installed the required Windows prerequisites, install them as follows:1. To install the Windows hotfix, choose OK.2. Windows Server 2003:

Install the hotfix KB937444.3. When the installation is finished, reboot your

system.4. Restart the installation with setup.exe.

SQL Server Installation Center 1. Choose Installation.



2013-06-14 CUSTOMER 19/38

Window Input2. Choose Upgrade from SQL Server 2000 or SQL Server

2005.


Product Key If this window appears, enter the product key and choose Next.





Select Features NOTE

In this screen, the features to upgrade are pre-selected. You cannot change the features to be upgraded nor can you add any new features.

Choose Next.

Instance Configurations 1. Select the instance you want to install.2. Leave the default values in field Instance ID.3. Choose Next.


Server Configuration 1. Enter the same domain account that you entered on the first cluster node for SQL Full-text Filter Daemon Launcher. Otherwise, leave the same default values as on the first node.

2. Choose Next.

Full Text Upgrade 1. Enter the same option for Full Text Upgrade that you entered on the first cluster node.

2. Choose Next.



Cluster Upgrade Report Review the report and choose Next.

Ready to Upgrade Review the summary list and choose Upgrade.

Upgrade Progress You can monitor the upgrade progress of the selected features in this screen.When the upgrade has finished, choose Next.

Cluster Upgrade Report This screen displays the current upgrade status of the cluster nodes in your SQL Server failover cluster.Choose Next.



20/38 CUSTOMER 2013-06-14

Window Input

Complete After the upgrade has been completed, choose Close to finish the upgrade.

8. Install the latest Service Pack and the Cumulative Update. For more information, 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.


9. Run the SAP tools for MS SQL Server.

The SAP tools for MS SQL Server perform the post-upgrade steps that are required for SAP ABAP

products running on SQL Server 2008 (R2). For more information about how to use and where to

download them, see SAP Note 683447.

10. Start the SAP system.

11. Connect with a database administrator logon to the SQL Server 2008 (R2) 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 2008 (R2)

statistics. You can execute this while the SAP system is online.

12. Change the page verify option with the following commands:

use master

go

alter database <SID> SET PAGE_VERIFY CHECKSUM;

go

13. 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. 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 2008 R2 SNAC client on these

hosts as described in Installing the SQL Server 2008 (R2) Native Client Software Manually [page 32].



2013-06-14 CUSTOMER 21/38



4 Installing SQL Server 2008 (R2) for a New SAP System

The following sections describe how to install the SQL Server 2008 (R2) 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.

For more information, see the following sections:

■ Installing the SQL Server Database Software Automatically with SQL4SAP [page 23].

■ Installing the SQL Server 2008 (R2) Database Server Software Manually [page 24].

■ Clustering the the SQL Server 2008 (R2) Database Server Software [page 27]

■ Installing the SQL Server 2008 (R2) Native Client Software Manually [page 32].

4.1 Installing the SQL Server Database Software Automatically with SQL4SAP

With SQL4SAP.VBS, you can automatically install the SQL Server 2008 (R2) database software on various

Windows operating systems.

NOTE

The SQL4SAP script installs both the SQL Server database server and Native Access Client software

automatically.

For more information about installing with SQL4SAP.VBS, see Customized Installation of SQL Server for an SAP

System with SQL4SAP.VBS (SQL4SAP_docu.pdf) and the readme.txt, both of which are located in the

root directory of the SQL Server RDBMS DVD.

CAUTION

■ Not all combinations of SQL Server and Windows are supported by all SAP products. For up-

to-date information on the released and supported database versions for your SAP product

and database, see the Product Availability Matrix (PAM) at:



4.1 Installing the SQL Server Database Software Automatically with SQL4SAP

2013-06-14 CUSTOMER 23/38


■ Only valid for: HA (MSCS) |

You cannot use the SQL4SAP.VBS script to install a high availability system on Windows with

failover clustering. If you want to run the script in a high-availability environment, you receive

an error message.

For more information about installing the SQL Server database software for a high-availability

system, see Clustering the SQL Server 2008 (R2) Database Server Software [page 27].End of: HA (MSCS) |

You use the SQL4SAP.VBS script to automatically install:

■ The 64-bit SQL Server 2008 (R2) Enterprise Edition

Only valid for: Upgrade |

CAUTION

You cannot use the SQL4SAP.VBS script to upgrade from SQL Server 2000 or SQL Server 2005

to SQL Server 2008 (R2), or from SQL Server 2008 to SQL Server 2008 R2.

End of: Upgrade |

■ The latest SQL Server 2008 (R2) service pack, cumulative update, or hot fix (if available)

■ Default Instances, Named Instances, or SQL Server Client Tools

For up-to-date information about installing SQL Server 2008 (R2) with SQL4SAP, read SAP Note

1144459.

Procedure

1. Insert the SQL Server RDBMS DVD into your DVD drive or copy it locally.

2. Double-click SQL4SAP.VBS located in the root directory.

3. Follow the instructions and enter the required information in the installation screens.

4. After the SQL Server installation has finished successfully, set the SQL Server Agent configuration [page

35].

4.2 Installing the SQL Server 2008 (R2) Database Server Software Manually

You have to install the SQL Server 2008 (R2) database server software on the database host.

Prerequisites

SQL Server 2008 (R2) requires Microsoft .NET Framework 3.5 (x64).

■ Windows Server 2008 R2:








24/38 CUSTOMER 2013-06-14



■ Windows Server 2008:

Install or update the Microsoft .Net Framework as follows:


2. Insert the SQL Server 2008 RDBMS DVD or SQL Server 2008 R2 RDBMS DVD in your DVD

drive or copy it locally.

3. For x64, run the executable dotNetFx35setup.exe, which is located in the following directory:

● SQL Server 2008:


● SQL Server 2008 R2:


\<platform>

4. Accept the licensing terms for the .Net Framework and choose Install.

5. After the installation of the .Net Framework is finished, reboot your system.

Procedure

1. Log on as a user who is a member of the local Administrators group.

2. Insert the SQL Server 2008 RDBMS DVD or SQL Server 2008 R2 DVD in your DVD drive or copy

it locally.

3. Change to the directory x86-x64-IA64\EnterpriseEdition on the RDBMS DVD.

4. Start the SQL Server database software installation with setup.exe.

NOTE

Make sure that you have installed or updated the Microsoft .Net Framework as described

under Prerequisites.


NOTE

The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL Server

\100\Setup Bootstrap\LOG\<YYYYMMDD_HHMM>. You find the summary of the setup log in

Summary_<HOSTNAME><YYYYMMDD_HHMM>.txt in the same directory.

Input for the MS SQL Server 2008 (R2) Installation

Window Input

Microsoft SQL Server 2008 (R2) Setup The Microsoft SQL Server 2008 (R2) setup requires Windows prerequisites, such as the Microsoft .NET Framework and an updated Windows installer.1. To install the required Windows prerequisites, choose OK.2. Reboot your system, if required.

SQL Server Installation Center Use the System Configuration Checker to check your system configuration and, if required, set up the required configuration.For more information about the required system configuration for the software components, check the SQL Server Books Online.



2013-06-14 CUSTOMER 25/38

Window Input

SQL Server Installation Center 1. Choose Installation.2. Select New SQL Server standalone installation or add features to an existing

installation.

Product Key If this window appears, enter the product key.




SQL Server 2008 R2 only:Feature Role

Select SQL Server Feature installation and choose Next.

Feature Selection 1. Select all features, except: ■ SQL Server Replication

■ Analysis Services

■ Reporting Services

■ Integration Services

■ Microsoft Sync Framework2. Choose Next.

Instance Configuration 1. 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.

2. Leave the Instance ID and Instance root directory field to the default values.

3. Choose Next.

Disk Space Requirements Choose Next.

Server Configuration 1. In the Service Accounts tab, perform the following steps:1. Enter the Local System accounts

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 to change the collation.

3. When you have made all entries, choose Next.

Database Engine Configuration 1. In the Account Provisioning 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.



26/38 CUSTOMER 2013-06-14

Window Input2. 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 AddIn the Select Users or Groups window, choose one Windows account as local system administrator.SAP strongly recommends that you enter Administrators in the Select Users or Groups window, to add the BUILTIN\Administrators (Administrators) users.

4. Choose Next.

Error Reporting Choose Next.

Installation Rules If there are no failed operations or warnings, choose Next. Otherwise, first check the warnings.

Ready to Install Select Install.

Installation Progress You can monitor the installation progress of selected features in this screen.

Complete After the installation has been completed, choose Close to finish the installation.

6. When you have finished the installation, enable the Named Pipes and TCP/IP protocol in the SQL

Server Configuration Manager as follows:




■ For a default instance, select Protocols for MSSQLServer


3. In the right-hand pane, under Protocol Name, right-click Named Pipes and TCP/IP, and select

Enable.



62988.


4.3 Clustering the SQL Server 2008 (R2) Database Server Software

This section describes how to install the SQL Server 2008 (R2) database server software for a high-

availability system with Microsoft failover clustering.

The SQL Server 2008 (R2) database server software must be installed on the database host.



2013-06-14 CUSTOMER 27/38


NOTE

The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL Server\100

\Setup Bootstrap\LOG\<YYYYMMDD_HHMM>. You can find the summary of the setup log in

Summary_<HOSTNAME><YYYYMMDD_HHMM>.txt in the same directory.

To install the client software for an application server, see Installing the SQL Server 2008 (R2) Native Client

Software Manually [page 32].

Prerequisites

■ SQL Server 2008 (R2) requires Microsoft .NET Framework 3.5 (x64).













3. For x64, run the .Net Frameworks executable dotNetFx35setup.exe, which is located in

the following directory:

◆ SQL Server 2008:


◆ SQL Server 2008 R2:


\<platform>


5. After the installation of the .Net Frameworks is finished, reboot your system.

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 2008 RDBMS DVD in your DVD drive or copy it locally.


x86-x64-IA64\EnterpriseEdition.



28/38 CUSTOMER 2013-06-14

5. Start the installation program with setup.exe on the first cluster node.

NOTE




Input for the MS SQL Server 2008 (R2) Installation on the First Cluster Node

Window Input

Microsoft SQL Server 2008 (R2) Setup The Microsoft SQL Server 2008 (R2) setup requires Windows prerequisites, such as the Microsoft .NET Framework and an updated Windows installer.1. To install the required Windows prerequisites, choose OK2. When the installation of the prerequisites is finished, reboot your

system.When you reboot your system, make sure that all the cluster resources and groups are owned by the first cluster node.

3. Restart the installation with setup.exe.

SQL Server Installation Center To check your system configuration, use the System Configuration Checker. If required, set up the required configuration.For more information about the required system configuration for the software components, check the SQL Server Books Online.

SQL Server Installation Center 1. Choose Installation.2. Select New SQL Server failover cluster installation.

Product Key If this windows appears, enter the product key and choose Next.




SQL Server 2008 R2 only:Feature Role

Select SQL Server Feature installation and choose Next.

Feature Selection 1. Select all features, except: ■ Analysis Services

■ Reporting Services

■ Integration Services

■ Microsoft Sync FrameworkIn a failover cluster installation, the features SQL Server Replication and Text Search are mandatory and you cannot deselect them.

2. Choose Next.

Instance Configuration 1. Enter the SQL Server network name.2. Select the instance type that you want to install.

Since the configuration of SQL Server is easier to handle, we recommend that you select Default instance. ■ If you want to install a Named instance, enter the <SAPSID> in

the Named instance field. ■ If you want to install multiple SAP systems with multiple SQL

Server instances you must select Named instance.3. Leave the default values in field Instance ID and Instance root directory.



2013-06-14 CUSTOMER 29/38

Window Input4. Choose Next.


Cluster Resource Group Specify the SQL Server cluster resource group and choose Next.

Cluster Disk Selection 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.

Cluster Security Policy We recommend that you leave the selection unchanged. Choose Next.

Server Configuration 1. In the Service Accounts tab, enter the domain accounts and passwords.In the Server Configuration window, do not use the Browse button to specify a domain account for a specific service in the Account Name text box.For more information, see Microsoft Knowledge Base article 955948.

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 button.

3. When you have made all entries, choose Next.

Database Engine Configuration 1. In the Account Provisioning tab, select one of the following authentication modes: ■ Windows authentication mode

SAP recommends 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. Choose Add to specify an SQL Server administrator.In the Select Users or Groups window, choose one Windows account as local system administrator.SAP strongly recommends that you enter Administrators in the Select Users or Groups window.

4. Choose Next.

Error Reporting Select the required error reporting and choose Next.

Cluster Installation Rules If there are no failed operations or warnings, choose Next. Otherwise, first check the warnings.



30/38 CUSTOMER 2013-06-14

Window Input

Ready to Install Check the summary list and choose Install.

Installation Progress You can monitor the installation progress of selected features in this screen.


7. When you have finished, complete the cluster installation by restarting the installation program

with setup.exe on the second cluster node.

NOTE




Input for the MS SQL Server 2008 (R2) Cluster Installation Completion on the Second Node

Window Input

Windows Update Standalone Installer 1. To install the Windows hotfix, choose OK.2. When the installation of the hotfix(es) is finished, reboot your

system.3. Restart the installation with setup.exe.

SQL Server Installation Center 1. Choose Installation.2. Select Add node to a SQL Server failover cluster.


Product Key If this windows appears, enter the product key and choose Next.




Cluster Node Configuration Select the SQL Server instance name and choose Next.

Service Accounts 1. Enter the same domain user(s) and password(s) that you entered for the services SQL Server Database services and SQL Server Agent on the first cluster node.

2. Choose Next.

Error and Usage Reporting Settings Choose Next.

Add Node Rules If there are no failed operations or warnings, choose Next. Otherwise, first check the warnings.

Ready to Add Node Check the summary list and choose Install.

Add Node Progress You can monitor the installation progress of selected features in this screen.


9. When you have finished, enable the Named Pipes and TCP/IP protocol in the SQL Server Configuration

Manager on all cluster nodes as follows:



2013-06-14 CUSTOMER 31/38




■ For a default instance, select Protocols for <SQL Server Instance Name>


3. In the right-hand pane, under Protocol Name, right-click Named Pipes and TCP/IP, and choose

Enable.


11. After the SQL Server 2008 (R2) 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.


62988.

Perform the following steps to install the SQL Server updates:


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.


13. Test the failover of the SQL Server group between the cluster nodes.

14. Perform the following steps:

1. Start the Failover Cluster Management, and take the SQL Server resource offline in the SQL Server

application.

2. In the Services and Applications node, double-click the SQL Server or SQL Server(<NamedInstance>)

application.

3. In the left-side window, take the SQL Server resource offline.

Right-click the SQL Server or SQL Server(<NamedInstance>) and select Properties.

4. In the Dependencies window, use the insert button and add the shared disks that are used for

database files with the AND operator.


4.4 Installing the SQL Server 2008 (R2) Native Client Software Manually

This section describes how to install the SQL Server 2008 (R2) Native Access Client (SNAC) software.

You have to install the SQL Server 2008 (R2) client software on all SAP application servers. It enables

the communication between an application server and the database.



32/38 CUSTOMER 2013-06-14


Procedure

1. Log on as local administrator to the host where you want to install an application server.

2. Insert the SQL Server 2008 or SQL Server 2008 R2 RDBMS DVD in your DVD drive or copy it locally.

3. Change to the directory <RDBMS_DVD>:\SqlNativeClient\<platform>\ and double-click the

SNAC files.

For more information, see SAP Note 1144459.

4. Follow the instructions in the SQL Server installation setup screens.



2013-06-14 CUSTOMER 33/38


5 Setting the SQL Server Agent Configuration

After you have installed or upgraded to SQL Server 2008 (R2), 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.

5 Setting the SQL Server Agent Configuration

2013-06-14 CUSTOMER 35/38

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

36/38 CUSTOMER 2013-06-14

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2013 SAP AG. 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 AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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 AG in Germany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

DisclaimerPlease see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

2013-06-14 CUSTOMER 37/38

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://www.sap.com/corporate-en/legal/copyright/index.epx


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2013 SAP AG. 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 AG. The information contained herein may be changed without prior notice.

Sql2008r2 Upgrade v150

Documents

Transcript of Sql2008r2 Upgrade v150