Installation GuideCustomized Installation of SQL Server 2008 for an SAP Systemwith SQL4SAP.VBS

Target Audience

n Technology Consultantsn System Administrators

PUBLICDocument version: 1.00 ‒ 09/16/2008

Document History

The following table provides an overview on the most important document changes:

Version Date Description

1.00 9/16/2008 Initial Version

2/20 PUBLIC 09/16/2008

Table of Contents

Chapter 1 Customized Installation of SQL Server 2008 for an SAP System withSQL4SAP.VBS . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 Additional Information . . . . . . . . . . . . . . . . . . . 13

09/16/2008 PUBLIC 3/20

4/20 PUBLIC 09/16/2008

1 Customized Installation of SQL Server 2008 for an SAP System with SQL4SAP.VBS

1 Customized Installation of SQLServer 2008 for an SAP System withSQL4SAP.VBS

This documentation explains how to use the SQL4SAP.VBS script to install SQL Server 2008 foryour SAP system. For up-to-date information on the installation of SQL Server 2008 with SQL4SAP,see SAP Note 1144459.

Caution

The SQL4SAP.VBS script does not support high availability on Windows with failover clustering. Formore information about how to install your SQL Server database software for a high-availabilitysystem, see the installation guide for MS SQL Server.

Features

n With the SQL4SAP.VBS script you can install:l One of the following SQL Server 2008 editions:

u32-bit SQL Server 2008 Enterprise Edition on x86 systems (not supported by SAP)

u64-bit SQL Server 2008 Enterprise Edition on x64 systems

u64-bit SQL Server 2008 Enterprise Edition on IA64 systems

Caution

uSAP does not support the 32-bit edition of SQL Server 2008.

uSAP does not support SQL Server 2008 on all SAP products. For more information, see theProduct Availability Matrix (PAM) at: http://service.sap.com/platforms ProductAvailability Matrix .

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

Caution

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

l Default Instances, Named Instances, or SQL Server Client Tools onlyn During the installation an output console window appears that shows all installation steps at

all times.

09/16/2008 PUBLIC 5/20

1 Customized Installation of SQL Server 2008 for an SAP System with SQL4SAP.VBS

n In Windows Server 2008 and Vista, the following User Account Control windowmight appear:

Figure 1: User Account Control Window

Prerequisites

n You use one of the following 64-bit Windows operating systemsl Windows Server 2003 Editions

uWindows Server 2003 Standard Edition, SP2 or higher

uWindows Server 2003 Enterprise Edition, SP2 or higher

uWindows Server 2003 Datacenter Edition, SP2 or higherl Windows Server 2008 Editions:

uWindows Server 2008 Standard Edition

uWindows Server 2008 Enterprise Edition

uWindows Server 2008 Datacenter Edition

uWindows Server 2008 for Itanium-Based Systems Editionl Microsoft Installer (MSI) 4.5 or higherl Microsoft .Net Frameworks 3.5 SP1, 3.0 SP2, 2.0 SP2

Installing or Updating the Microsoft Installer with the SQL4SAP.VBS ScriptAn up-to-date version of the Microsoft Installer (MSI) is required for the installation of SQL Server2008. You can use the SQL4SAP.VBS script to install or update the MSI if required.

1. Double-click the SQL4SAP.VBS script located in the root directory of your SQL Server 2008 RDBMSDVD.A pop-up appears informing you that SQL Server 2008 requires an updated MSI.

6/20 PUBLIC 09/16/2008

1 Customized Installation of SQL Server 2008 for an SAP System with SQL4SAP.VBS

Figure 2: Update MSI Window

2. Close the pop-up window and install or update the MSI.The installer directly takes you to the directory where you can find the program file for the MSIpackage.

3. Install the MSI by double-clicking one of the following files:n For Windows Server 2003, double-click INSTMSI45.EXEn For Windows Server 2008, double-click INSTMSI45.MSU

4. If required, reboot your system, after the installation has finished.

Installing the SQL Server 2008 including Microsoft .NetThis procedure describes how to install SQL Server 2008, including the required Microsoft .NetFrameworks (if not already installed).

1. Double-click the SQL4SAP.VBS script located in the root directory of your SQL Server 2008 RDBMSDVD.The Select SQL Server 2008 instance window appears.

Note

If you do not have an installed an up-to-date MSI, you are asked to install or update it. Werecommend that you do so as described above

2. Provide the required information in the Select SQL Server 2008 instance window:

09/16/2008 PUBLIC 7/20

1 Customized Installation of SQL Server 2008 for an SAP System with SQL4SAP.VBS

Figure 3: Select SQL Server 2008 Instance Window

n To install a Default Instance, (default) choose OK.We recommend you to install a default instance.

n To install a Named Instance, enter the <SID> and choose OK.n To install the SQL Server Client Tools only software for monitoring your SAP system, choose Cancel.

Note

l This option is not available if the SQL Server Client Tools software is already installed.

l If you install an SAP application server, you require the SQL Server Native Client(SNAC) instead. You can find the SNAC files on the SQL Server 2008 RDBMS DVDin the directory: <RDBMS_DVD>:\x86-x64-ia64\SqlNativeClient\<platform>\sqlncli_xxx_<platform>.msi

n To install the latest service pack, cumulative update or hot fix (not yet available at time ofpublication) for an already existing SQL Server instance, enter the SQL Server instance nameand choose OK.

The Confirmation window appears.

8/20 PUBLIC 09/16/2008

1 Customized Installation of SQL Server 2008 for an SAP System with SQL4SAP.VBS

Figure 4: Confirmation Window

3. Check your entries and choose OK to start the SQL Server installation.The Update .Net Frameworks window appears informing you that SQL Server 2008 requires Microsoft.Net Framework.

Figure 5: Update .Net Frameworks Window

4. Choose one of the following options:n If you have not yet installed the required .Net Frameworks, choose Yes to install them.

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

09/16/2008 PUBLIC 9/20

1 Customized Installation of SQL Server 2008 for an SAP System with SQL4SAP.VBS

b) Restart the SQL4SAP.VBS script.The script takes you back to the Confirmation screen (see previous step).

c) Choose OK to start the installation of SQL Server 2008.n If you have already installed and updated the .Net Frameworks choose No to start the SQL

Server 2008 installation.

Note

Although you have already installed the required .Net Frameworks, we recommend thatyou choose Yes and update them.

Caution

Do not close the output console window, which shows all installation steps at all times. Afterthe SQL4SAP window has closed, check the SQL4SAP.log file, which is located in the WINDOWSdirectory. The log file contains all installation steps, return codes, and SQL commands.

Figure 6: Output Console Window

When the installation is finished, the Installation finished successfully window appears.

10/20 PUBLIC 09/16/2008

1 Customized Installation of SQL Server 2008 for an SAP System with SQL4SAP.VBS

Figure 7: Installation Finished Successfully Window

09/16/2008 PUBLIC 11/20

This page is intentionally left blank.

2 Additional Information

2 Additional Information

The SQL4SAP.VBS script installs Microsoft SQL Server inWindows Authenticationmode. The scriptdisables the sa login and sets a random password for the sa login. If you want to use the sa login, youmust change the authentication mode into SQL Server and Windows Authenticationmode, enable the salogin and set its password, as described below.

Changing the Windows Authentication Mode into SQL Server and WindowsAuthentication ModeTo use SQL Server and Windows Authenticationmode, you have the following options:

n You use the script _SqlAuth.vbs, which is located in the root directory on the RDBMS CD, toautomatically install SQL Server 2008 with authentication mode SQL Server and Windows Authentication.

Note

A Java system requires the SQL Server and Windows Authenticationmode.

n You manually change the authentication mode fromWindows Authentication to SQL Server and WindowsAuthentication in the SQL Server Management Studio as follows:1. Choose All Programs Microsoft SQL Server 2008 SQL Server Management Studio .2. In the Connect to Server window, enter the server name (if required), and choose Connect.3. Right-click the SQL Server instance and choose Properties.4. Choose Security.5. For Server authentication, choose SQL Server and Windows Authenticationmode.6. Choose OK.7. Restart SQL Server.

09/16/2008 PUBLIC 13/20

2 Additional Information

Figure 8: Changing the Authentication Mode

Setting and Enabling the Password for the SQL Server Login saTo set the password for the sa login, you use the SQL Server Management Studio:

1. Choose All Programs Microsoft SQL Server 2008 SQL Server Management Studio .2. In the Connect to Server window, enter the server name (if required), and choose Connect.3. Choose the SQL Server instance Security Logins .4. Right-click sa and choose Properties.5. Under General, enter and confirm the password for the sa login.6. Under Status, choose Login Enabled.7. Choose OK.

14/20 PUBLIC 09/16/2008

2 Additional Information

Figure 9: Setting a the Password for the SQL Server Login sa

Figure 10: Enabling the Password for the SQL Server Login sa

09/16/2008 PUBLIC 15/20

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriateentries 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 thedocumentation

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 tospecific content on the Web

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

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

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn 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 languagewhen they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

16/20 PUBLIC 09/16/2008

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

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

www.sap.com

© Copyright 2008 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 permissionof 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 othersoftware vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof 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 othersoftware 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 SystemsIncorporated 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 registeredtrademarks 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 implementedby Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves informational purposes only. Nationalproduct 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 notbe liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2from Michael Kay (http://saxon.sf.net/), XSLT version 1.

09/16/2008 PUBLIC 17/20

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified oraltered in any way.

18/20 PUBLIC 09/16/2008

This page is intentionally left blank.

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

© Copyright 2008 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 bechanged without prior notice.