SAP Note No. 209596 15.10.2003 Page 1 ________________________________________________________________________ Number 209596 Version 16 from 14.01.2003 Status Released for Customer Set on 14.01.2003 Language EN Master language EN Short text Setting up Microsoft SQL Server 2000 Responsible SAP AG Component BC-DB-MSS Microsoft SQL Server ________________________________________________________________________ Long text Symptom Setting up and running SQL Server 2000 for an SAP System and information on the upgrade from SQL Server 7.0 to SQL Server 2000. Additional key words SQL Server 7.0, multiple instances, named instance Cause and preconditions Additional up-to-date information for SQL 2000 Solution CONTENTS I IMPORTANT GENERAL REMARKS II UPGRADE FROM MS SQL SERVER 7.0 to 2000 a) UPGRADE IN A STANDARD SAP SYSTEM CONFIGURATION b) UPGRADE IN A MSCS SAP SYSTEM CONFIGURATION III GENERAL MS SQL SERVER 2000 INFORMATION IV MULTIPLE INSTANCES ON MS SQL SERVER 2000 V CLUSTER INSTALLATION ON MS SQL SERVER 2000 ======================================================================= I IMPORTANT GENERAL REMARKS ======================================================================= o Only the Enterprise Edition of SQL Server 2000 may be used in an SAP environment. o SQL Server 2000 is only supported on Windows 2000 with at least SP1. Windows NT 4.0 is not supported.

o Whether an SAP product may be used on SQL Server 2000 depends on the availability of the database monitor for that product. Refer Page 2 to note 139945 for details. ======================================================================= II UPGRADE FROM MS SQL SERVER 7.0 to 2000 ======================================================================= a) Upgrading in a Standard SAP system Configuration The following describes the steps you have to perform to upgrade from SQL Server 7.0 to 2000 in an SAP environment. Note that besides upgrading the server, you have to carry out some steps required specially for the SAP System. No other method of upgrading than the one described here is supported by SAP! Perform the following steps in the given order: Import Transports resp. hot-/support-packages before the database software upgrade. These transports/packages enable the DB monitor (DB02, DB12, DB13, ST04, and RZ20 as of 4.6B) to run on SQL Server 7.0 as well as on SQL Server 2000. Please refer to note 139945 to find out the actions necessary for your system. Only SAP products listed in note 139945 may be used on SQL Server 2000. 1. Shut down the SAP system. 2. Apply the latest patch for the kernel you are running. You have to download from http://service.sap.com/patches and unpack at least the archives dw1, dw2, R3load, R3trans, tp, and as of 4.5B also lib_dbsl. Always take the file with the highest number. If, for example, tp_437.CAR and tp_473.CAR are available, then take tp_473.CAR. Note For systems running with a 4.6 basis the 4.6D kernel is required for SQL Server 2000. So if your system is running with a 4.6B or 4.6C basis and you do not yet have the 4.6D kernel installed then you have to install the 4.6D kernel now and apply afterwards the latest patch. 3. Only for BW 1.2B; Replace the ntbwanly.dll. These steps must not be performed for any other SAP product! a) Execute the following two commands one after the other via Query Analyzer in the master database: exec sp_dropextendedproc 'ntbw_execute' dbcc ntbwanly (free) b) Stop SQL Server. c) Delete ntbwanly.dll from \mssql7\binn, \sys\exe\run, and

\system32 on your database server if it exists there. Do the same on each application server. d) Copy ntbwanly.dll from directory addons\bw_12b\ntbwanly on the xyz CD to the directory \system32 on your database server. Do the same on each application server. Page 3 e) Restart SQL Server and the SQL Server Agent. f) Execute the following command via Query Analyzer in the master database: exec sp_addextendedproc 'ntbw_execute', 'ntbwanly.dll' 4. Execute the stored procedure sap_droproc without any input parameter via Query Analyzer in the <SID> database. The execution takes some time. 5. Make sure that you have a valid database backup. 6. Make sure that Windows 2000 with at least SP1 is installed. 7. Upgrading SQL Server on the database server Caution: In a MSCS configuration, follow the instructions in the section 'Upgrading SQL Server in a MSCS Configuration' below. a) Start the setup from the MS SQL Server 2000 CD. b) In the screen "Computer Name" make your selection. c) In the screen "Installation Selection" choose "Upgrade, remove, or add components to an existing instance of SQL Server". d) In the screen "CD Key" enter the key specified in the file SAPCDKEY.txt in the root directory on the MS SQL Server 2000 CD. e) In the screen "Instance Name" flag "Default". f) In the screen "Existing Installation" choose "Upgrade your existing installation". g) In the screen "Upgrade" flag "Yes, upgrade my SQL Server Tools and data". h) Choose on the next screen "Connect to Server" the option "The Windows account information I use to log on to my computer with (Windows authentication)" if you are using SAP release 4.6C or higher. In all other cases choose "The SQL Server system administration login information (SQL Server authentication)" and type in the password of your sa. i) In the screen "Start Copying Files" choose "Next". j) In the screen "Choose Licensing Mode" choose your license model.

k) Now finish the setup. 8. If the SQL statement select count(*) from sysperfinfo executed via Query Analyzer in the master database returns 0 then, in a command window, switch to the directory \x86\binn on the SQL Server CD and execute the following command: Page 4 lodctr sqlctr.ini 9. Stop and restart SQL Server and the SQL Server Agent. 10. Execute the stored procedure sp_updatestats without any input parameter via Query Analyzer in the <SID> database. The execution takes some time. 11. Upgrade the SQL Server Client Tools on all application servers. The procedure is similar to upgrading the SQL Server on the database server except the following steps: a) In the screen "Installation Selection" choose "Create a new instance of SQL Server or install Client Tools" b) In the screen "Installation Definition" choose "Client Tools only" Note: Windows 2000 with at least SP1 is required on the application servers, too. 12. Start the SAP system. In rare cases, the SQL Server upgrade may fail with an error message saying: "Error: Running script messages.sql". If this happens, please review the Microsoft Knowledge Base Article # Q300676 and apply the patch described therein. Once this patch has been applied, you can "resume/restart" the SQL Server 7.0 upgrade to SQL Server 2000. Page 5 b) Upgrading in a MSCS SAP System Configuration

The process consists of 5 phases Phase 1: Perform steps for an upgrade in a standard system

configuration

Perform steps 1-6 in the section 'Upgrading in a Standard SAP System Configuration' above. After this, instead of performing Step 7, 'Upgrading SQLServer on the DB server', continue with phases 2 -4 below.

Phase 2: Steps to uncluster sql server 7.0.

Bring the R3 group offline and stop the R3 services. Start the failover cluster wizard. 1. In the first 'Sql cluster setup option' screen select the option 0 Remove virtual server Enter the server name: Virtual Server Name 2. What is the sa password for sql server on this computer: ( setup checks whether it is safe to uninstall the cluster) 3. sqlserver is ready to finish the removal of virtual server from the cluster. Do you want sql server setup to finish. If so, select 'finish' button. 4. If you get a message 'sql server binaries could not be updated', then close the sql manager and try again. 5. If the Virtual server is removed sucessfully, then the message 'Virtual server has been removed sucessfully' will appear. Reboot the Node A. Phase 3: Upgrading SQL Server on the database server

1. Start the setup from the MS SQL Server 2000 CD. 2. In the screen "Computer Name" make your selection. 3. In the screen "Installation Selection" choose "Upgrade, remove, or add components to an existing instance of SQL Server". 4. In the screen "CD Key" enter the key specified in the file SAPCDKEY.txt in the root directory on the MS SQL Server 2000 CD. 5. In the screen "Instance Name" flag "Default". 6. In the screen "Existing Installation" choose "Upgrade your existing installation". 7. In the screen "Upgrade" flag "Yes, upgrade my SQL Server Tools and data". Page 6 Message popup: "Setup has detected tha program files are installed on a cluster resource, During upgrade setup will install new program files in the location you select and remove the old program files in order to allow an upgrade later to cluster installation 8. Choose on the next screen "Connect to Server" the option "The Windows account information I use to log on to my computer with (Windows authentication)" if you are using SAP release 4.6C or higher. In all other cases choose "The SQL Server system

administration login information (SQL Server authentication)" and type in the password of your sa. 9. Setup will display a 'setup type screen' for destination folders Program files: Drive Letter:\..\Microsoft Sqlserver\ MSSQL Data files : Drive Letter:\mssql7 ( or your sql date directory) (grayed out) This screen will take few minutes 10. In the screen "Start Copying Files" choose "Next". 11. In the screen "Choose Licensing Mode" choose your license model. 12. Now finish the setup. Reboot Node A and Node B Before starting the upgrade to sql server, make sure - all the groups are owned by node A - The authentication for sql server should be both sql server and windows NT. You can check this in SQL EM and by right clicking and select properties in the server. Then in sql server properties screen, select 'security'. 13. run the file SQLVERFIX.REG The file is available in the SAPNet at http://service.sap.com/msplatforms under "Utilities" Phase 4: Run the setup from the sql server installation Cd.

1. In the screen "computer Name", select "local computer" 2. In the screen " installtion selection", select " upgrade, remove, or add components to an existing instance of sql server " 3. In the screen "Instance name", Default option is automatically selected.if not Select "default" This will take few minutes 4. In the screen "Existing installtion screen" Select "Upgrade your existing installtion to a clustered installtion" Page 7 5. In the screen for virtual server: Enter the virtual server name 6. In the screen failover clustering Enter the ip-address and subnet mask for virtual server This will take few minutes. 7. In the screen cluster management, select the nodes for cluster

management(both nodes) 8. In the screen remote information, enter a domain adminstrator user who can adminstrator both nodes and password. 9. In the screen service account, enter a domain administrator user account for both nodes. This will take few minutes. 10. In the screen "Choose Licensing mode", Select Finish to finish the setup. 11. In the screen setup complete screen, a successful msg will be displayed. Reboot node A and then bring the r3 group online. PHASE 5: Completing the Upgrade

Perform the steps 8-13 in the section 'Upgrading in a standard SAP System configuration' above. ======================================================================= III GENERAL MS SQL SERVER 2000 INFORMATION ======================================================================= Installation of 46C or 46D If an error message appears when you start the SAP Management Console or when you add the SAP snap-in to the console, please refer to the SAP Note 354595. ======================================================================= IV MULTIPLE INSTANCES ON MS SQL SERVER 2000 ======================================================================== For information on this topic see the paper 'Installation of MS SQL 2000 in an SAP Environment' This is available on the MS SQL Tools CD in the file readme.pdf ======================================================================= V CLUSTER INSTALLATION ON MS SQL SERVER 2000 ======================================================================= MSSQL 2000 on MSCS under Windows 2000 is supported for various SAP releases. The installation is described in a document which is available under http://service.sap.com/instguides -> "Database Upgrades" -> "MS SQL" -> "Installation of MS SQL 2000 in an SAP Environment". Source code corrections ________________________________________________________________________ Page 8 Valid releases Software Component Release from to SAP_APPL SAP Application 46C - 46C 46B - 46B 45A - 45B 40B - 40B

SAP_BW Business Information Warehouse 20B - 20B 12B - 12B SAP_BASIS SAP Basis component 46D - 46D ________________________________________________________________________ Note attributes Transaction codes COPY DB02 Transaction codes DB12 DB13 Transaction codes FILE MODE Transaction codes RZ20 ST04 Transaction codes TIME Operating system NT/INTELWIN2000 Database system MSSQLSRV7.0 MSSQLSRV8.0 ________________________________________________________________________ Reference to related Notes Number Short text ____________________________________________________________ 497446 Upgrading to SQL 2000 stops when executing Upgrade.sql 505906 SQL error 446: Cannot resolve collation conflict 401836 Migration Oracle 8.1.7 => SQL Server 2000 192658 Setting basis parameters for BW Systems 156558 Released SAP Kernel 4.6x MS SQL Server operat. sys. 377430 SQL Server 2000 installation CD of SAP 327494 Configuration Parameters for SQL Server 2000 139945 SAP Database Monitor for MS SQL Server 353654 Additional Info: SQL Server 2000 for Asia ________________________________________________________________________