Upgrade MS SQL 2005 to MS SQL 2008 (R2) for Non-High-Availability NW Mobile ABAP System

Transcription

1 Upgrade MS SQL 2005 to MS SQL 2008 (R2) for Non-High-Availability NW Mobile ABAP System Applies to: SAP Netweaver Mobile 710/711 systems. For more information, visit the Mobile homepage. Summary This document serves as a guide which describes the necessary steps to upgrade a MS SQL Server 2005 to MS SQL Server 2008 (R2). Author: Abhishek Joshi Company: SAP Labs India Pvt. Ltd. Created on: 16 December 2010 Author Bio Abhishek Joshi is working in the Netweaver Mobile Engineering Services team as Senior Software Enggineer (Build and Production team ) SAP AG 1

2 Table of Contents Introduction... 3 Pre-requisites... 4 Pre-Upgrade steps... 6 Stopping ABAP engine... 6 Stopping engine service... 6 Backup of <SAPSID> DB Instance... 7 Upgrading MS SQL 2005 to 2008 (R2) for Non-High-Availability SAP NW Mobile System... 8 Post installation steps Setting MS SQL Server 2008 (R2) Run the SAP tools for MS SQL Server Related Content Copyright SAP AG 2

3 Introduction This document serves as a guide which describes the necessary steps to upgrade a MS SQL Server 2005 to MS SQL Server 2008 (R2) on Non-High-Availability Netweaver Mobile 710/711 system. An upgrade to MS SQL Server 2008 (R2) includes following steps. 1. Pre-requisites 2. Pre-installation steps 2.1. Stopping ABAP engine 2.2. Stopping engine service 2.3. Taking back-up of instance DB 3. Upgrading MS SQL 2005 to 2008 (R2) for Non-High-Availability SAP NW Mobile System 4. Post installation steps 4.1. Setting MS SQL Server 2008 (R2) 4.2. Run the SAP tools for MS SQL Server We will look at each step in more detail below SAP AG 3

4 Pre-requisites If you want to upgrade MS SQL Server 2005 for an existing SAP system, you must meet the following prerequisites: 1. You use Windows Server 2003 SP2 or higher. 2. 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). 3. 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. 4. You can find these patches on SAP Service Marketplace. 5. 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). 6. If you installed the 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. 7. 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. 8. You have backed up your SQL Server database. 9. You have shut down the SAP system. 10. 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: Log on as local administrator Open an elevated command prompt Enter the following command: servermanagercmd install NET-Framework-Core Reboot your system Windows Server 2008 (or lower): Install or update the Microsoft.Net Frameworks as follows: Log on as a local administrator Insert the SQL Server 2008 RDBMS DVD or SQL Server 2008 R2 RDBMS DVD in your DVD drive or copy it locally Run one of the following.net Frameworks executables: For x64, run the executable dotnetfx35setup.exe, which is located in the following directory: 2010 SAP AG 4

5 SQL Server 2008: x86-x64-ia64\enterpriseedition\<platform>\redist\dotnetframeworks 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\ Accept the licensing terms for the.net Frameworks and choose Install After the installation of the.net Frameworks has finished, reboot your system SAP AG 5

6 Pre-Upgrade steps Before starting upgrade of MS SQL Server 2005 to 2008 (R2), please do below mentioned steps. These steps are necessary to be executed. Stopping ABAP engine You need to login to system where you have ABAP serer installed as an Administrator. Start SAP MMC. Right click on ABAP Server Instance (In this document, we are working on J10 instance) and select Stop. It will ask you user name and password, please provide Administrator credentials. Stopping engine service It s very important to stop running ABAP engine services because ABAP engine will be accessible database and due to this you may encounter some issue during your DB Server upgrade. For this, open service manager (Start -> Run -> services.msc). Stop all running SAP<SAPSID>_* services. If we don t stop these services then in between upgrade of DB, engine will try to start by itself SAP AG 6

7 Backup of <SAPSID> DB Instance It s very important to take backup before we start our upgrade of DB to 2008 (R2). To do this follow below steps: 1. Start SQL Server Management studio (Start -> Programs -> Microsoft SQL Server > SQL Server Management Studio). 2. Connect to SQL server by providing credentials. 3. Right click on <SAPSID> DB, go to Tasks and select Back Up 4. Take Full Backup of <SAPSID> DB and provide location to keep it and click on OK SAP AG 7

8 It will take some time to finish the backup. Once done, you will get prompt message. Make sure that your Backup is successful and then only proceed with next steps. Upgrading MS SQL 2005 to 2008 (R2) for Non-High-Availability SAP NW Mobile System Before starting upgrade of MS SQL Server 2005, make sure that you completed pre-requisites and preupgrade successfully. Please follow below steps to perform upgrade of SQL server 2005 to 2008 R2. Start x86-x64-ia64\enterpriseedition\setup.exe. Select Installation -> Upgrade from SQL server 2000, SQL Server 2005 or SQL Server Installer will run Setup Support Rules. In case some rule fails then please fix them before going ahead SAP AG 8

9 Click OK, if all rule passed. Provide product key and click on Next SAP AG 9

10 Accept the license terms and click on Next. Click on Install so that installer will install support files, which is needed during upgrade of server SAP AG 10

11 Setup will check pre-requisites by running some rules. Click on Next only if there are no failed rules. Select your existing MS SQL server instance, which will be upgraded to NW SWL 2008 (R2) SAP AG 11

12 Setup will provide you list of features which will be upgraded to SQL Server (R2) release. Click on Next. Specify the name and instance ID for the instance of SQL Server. Instance ID becomes part of the installation path. Click on Next SAP AG 12

13 Setup will check the Disk space needed for upgrade. If it s OK then click on Next or if Disk space is less then free some space and Click on Back and come to this screen by pressing Next. If you want to user SQL Full-text Filter Daemon Launcher then provide your credentials and click Next SAP AG 13

14 Please select needed option (By default Import) and click on Next. Select Error Reporting information you want to send to Microsoft or your corporate report server. Click on Next SAP AG 14

15 Setup will run Upgrade rules and in case some rule fails then fix them before clicking on Next. If all rules are executed successfully, then click on Next. Setup will provide you all the options you have selected, in case you want to change something then please click on Back or if everything is fine and you want to start upgrade then click on Next. Once you click on Next button Upgrade will start and at the end you will get confirmation message of upgrade SAP AG 15

16 Post installation steps Setting MS SQL Server 2008 (R2) 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 2.1. For a default instance, select Protocols for MSSQLServer 2.2. 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. 4. Restart SQL Server SAP AG 16

17 Run the SAP tools for MS SQL Server This program performs the post-upgrade steps that are required for SAP ABAP products running on SQL Server 2008 (R2). For more information, see SAP Note Proceed as follows: 1. Download the zip file that includes the SAP tools for MS SQL Server from -> SQL Server 2. Extract it to an empty local directory on the database server. 3. Run sapinst.exe, and choose Upgrade to MS SQL Server 2005 or higher. 4. Start SAP<SID>_* services in services.msc. 5. Start the SAP system. 6. 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 7. 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 SAP AG 17

18 Related Content For more information, visit the Mobile Homepage SAP AG 18

19 Copyright Copyright 2010 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. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. 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 AG 19