SQL4SAP_docu

Installation GuideCustomized Installation of SQL Server 2008 R2 for an SAP System with SQL4SAP.VBS

Target Audience ■ Technology Consultants ■ System Administrators

PUBLICDocument version: 1.10 – 2011-08-19

Document History

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

Version Date Description

1.10 2011-08-19 Updated VersionContains SQL Server 2008 R2 SP1 incl. CU1 (10.50.2769) (SQL Server RDBMS DVD (#51041678))

1.00 2010-07-12 Initial Version

2/16 PUBLIC 2011-08-19

Table of Contents

Chapter 1 Customized Installation of SQL Server 2008R2 for an SAP System with

SQL4SAP.VBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 Installing or Updating the Microsoft Installer with the SQL4SAP.VBS

Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.2 Installing SQL Server 2008 R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1 Changing the Windows Authentication Mode into SQL Server and Windows

Authentication Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2 Setting and Enabling the Password for the SQL Server Login sa . . . . . . . . . . . . 12

2011-08-19 PUBLIC 3/16

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

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

This documentation explains how to use the SQL4SAP.VBS script to install SQL Server 2008 R2 for your

SAP system. For up-to-date information on the installation of SQL Server 2008 R2 with SQL4SAP, see

SAP Note 1144459.

CAUTION

The SQL4SAP.VBS script does not support high availability on Windows with failover clustering.

For more information about how to install your SQL Server database software for a high-

availability system, see the installation guide for MS SQL Server.

Features

■ With the SQL4SAP.VBS script you can install:

● One of the following SQL Server 2008 R2 editions:

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

◆ 64-bit SQL Server 2008 R2 Enterprise Edition on x64 systems

◆ 64-bit SQL Server 2008 R2 Enterprise Edition on IA64 systems

CAUTION

◆ SAP does not support the 32-bit edition of SQL Server 2008 R2.

◆ SAP does not support SQL Server 2008 R2 on all SAP products. For more information,

see the Product Availability Matrix (PAM) at:

http://service.sap.com/platforms Product Availability Matrix . ● The latest SQL Server 2008 R2 service pack, or cumulative update (if available)

CAUTION

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

or SQL Server 2008 to SQL Server 2008 R2.

● Default Instances, Named Instances, or SQL Server Client Tools only

■ During the installation an output console window appears that shows all installation steps at all

times.

■ If you have UAC enabled on your operating system, the following User Account Control window might

appear:


2011-08-19 PUBLIC 5/16

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

http://service.sap.com/platforms

Figure 1: User Account Control Window

Requirements

If you use SQL4SAP, you require:

■ One of the following 64-bit Windows operating systems:

● Windows Server 2003 Editions

◆ Windows Server 2003 Standard Edition, SP2 or higher

◆ Windows Server 2003 Enterprise Edition, SP2 or higher

◆ Windows Server 2003 Datacenter Edition, SP2 or higher

◆ Windows Server 2003 for Itanium-Based Systems Edition, SP2 or higher

● Windows Server 2008 Editions:

◆ Windows Server 2008 Standard Edition

◆ Windows Server 2008 Enterprise Edition

◆ Windows Server 2008 Datacenter Edition

◆ Windows Server 2008 for Itanium-Based Systems Edition

● Windows Server 2008 R2 Editions:

◆ Windows Server 2008 R2 Standard Edition

◆ Windows Server 2008 R2 Enterprise Edition

◆ Windows Server 2008 R2 Datacenter Edition

◆ Windows Server 2008 R2 for Itanium-Based Systems Edition

■ Microsoft Installer (MSI) 4.5 or higher

1.1 Installing or Updating the Microsoft Installer with the SQL4SAP.VBS Script

To install SQL Server 2008 R2, you require an up-to-date version of the Microsoft Installer (MSI). If

required, you can install or update the MSI using the SQL4SAP.VBS script.


1.1 Installing or Updating the Microsoft Installer with the SQL4SAP.VBS Script

6/16 PUBLIC 2011-08-19

Procedure

1. Double-click the SQL4SAP.VBS script located in the root directory of your SQL Server 2008 R2

RDBMS DVD.

A pop-up might appear, informing you that SQL Server 2008 R2 requires an updated MSI.

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 MSI

package.

3. Install the MSI by double-clicking one of the following files:

■ For Windows Server 2003, double-click INSTMSI45.EXE

■ For Windows Server 2008 or Windows Server 2008 R2, double-click INSTMSI45.MSU.

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

1.2 Installing SQL Server 2008 R2

This procedure describes how to install SQL Server 2008 R2.

Procedure

1. Double-click the SQL4SAP.VBS script located in the root directory of your SQL Server 2008 R2

RDBMS DVD.

The Select SQL Server 2008 R2 instance window appears.

NOTE

If you do not have an installed an up-to-date MSI, you are asked to install or update it. We

recommend that you do so as described above.

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



2011-08-19 PUBLIC 7/16

Figure 3: Select SQL Server 2008 R2 Instance Window

■ To install a Default Instance (default), choose OK.

We recommend that you install a default instance.

■ To install a Named Instance, enter the <SID> and choose OK.

■ To install the SQL Server Client Tools only software for monitoring your SAP system, choose

Cancel.

This option is not available if the SQL Server Client Tools software is already installed and is up-

to-date.

NOTE

If you install an SAP application server, you can also install the SQL Server Native Client

(SNAC) instead of the SQL Server Client Tools. You find the SNAC files on the SQL Server

2008 R2 RDBMS DVD in the directory: <RDBMS_DVD>:\SqlNativeClient\<platform>\

For more information, see SAP Note 1144459.

■ To install the latest service pack, or cumulative update (if available) for an already existing

SQL Server instance, enter the SQL Server instance name and choose OK.

■ To install the latest service pack, or cumulative update for already installed SQL Server Client

Tools, or for an already installed SNAC, choose Cancel.

The Confirmation window appears.



8/16 PUBLIC 2011-08-19


Figure 4: Confirmation Window

3. Check your entries and choose OK to start the SQL Server installation.

The output console window appears, which shows all installation steps at all times.

CAUTION

Do not close the output console window.

Figure 5: Output Console Window

4. After the SQL4SAP window has closed, check the SQL4SAP.log file, which is located in the

WINDOWS directory. The log file contains all installation steps, return codes, and SQL commands.

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



2011-08-19 PUBLIC 9/16

Figure 6: Installation Finished Successfully Window



10/16 PUBLIC 2011-08-19

2 Additional Information

The SQL4SAP.VBS script installs Microsoft SQL Server in Windows Authentication mode. The script disables

the sa login and sets a random password for the sa login. If you want to use the sa login, you must

change the authentication mode into SQL Server and Windows Authentication mode, enable the sa login and

set its password, as described below.

2.1 Changing the Windows Authentication Mode into SQL Server and Windows Authentication Mode

Procedure

To use SQL Server and Windows Authentication mode, you have the following options:

■ You use the script _SqlAuth.vbs, which is located in the root directory on the RDBMS CD, to

automatically install SQL Server 2008 R2 with authentication mode SQL Server and Windows

Authentication.

NOTE

A Java system requires the SQL Server and Windows Authentication mode.

■ You manually change the authentication mode Windows Authentication to SQL Server and Windows

Authentication in the SQL Server Management Studio as follows:

1. Choose All Programs Microsoft SQL Server 2008 R2 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 Authentication mode.

6. Choose OK.

7. Restart SQL Server.


2.1 Changing the Windows Authentication Mode into SQL Server and Windows Authentication Mode

2011-08-19 PUBLIC 11/16

Figure 7: Changing the Authentication Mode

2.2 Setting and Enabling the Password for the SQL Server Login sa

Procedure

To set and enable the password for the sa login, you use the SQL Server Management Studio:

1. Choose All Programs Microsoft SQL Server 2008 R2 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.



12/16 PUBLIC 2011-08-19

Figure 8: Setting the Password for the SQL Server Login sa

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



2011-08-19 PUBLIC 13/16

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

14/16 PUBLIC 2011-08-19

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 2011 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 BusinessObjects Explorer, 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 Software Ltd. in the United States and in other countries.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase 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.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe 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 or altered in any way.

2011-08-19 PUBLIC 15/16

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

© Copyright 2011 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.

SQL4SAP_docu

Documents

edition of sql server

following sql server

latest sql server

ms sql server

sql server login

sql server rdbms dvd

sql server client tools

sql server database