The following table provides an overview on the most important document changes:
Version Date Description
Chapter 1 Customized Installation of SQL Server 2008 for an SAP System with
SQL4SAP.VBS . . . . 5
1 Customized Installation of SQL
Server 2008 for an SAP System with
SQL4SAP.VBS
This documentation explains how to use the SQL4SAP.VBS script to install SQL Server 2008 for your SAP system. For up-to-date information on the installation of SQL Server 2008 with SQL4SAP, see SAP Note1144459.
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
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 the Product Availability Matrix (PAM) at: http://service.sap.com/platforms Product
Availability 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 2005 to SQL Server 2008.
l Default Instances, Named Instances, or SQL Server Client Tools only
n In Windows Server 2008 and Vista, the following User Account Control window might appear:
Figure 1: User Account Control Window
Prerequisites
n You use one of the following 64-bit Windows operating systems
l 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 higher
l 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 Edition
l Microsoft Installer (MSI) 4.5 or higher
l Microsoft .Net Frameworks 3.5 SP1, 3.0 SP2, 2.0 SP2
Installing or Updating the Microsoft Installer with the SQL4SAP.VBS Script
An up-to-date version of the Microsoft Installer (MSI) is required for the installation of SQL Server 2008. You can use the SQL4SAP.VBS script to install or update the MSI if required.
1. Double-click theSQL4SAP.VBSscript located in the root directory of your SQL Server 2008 RDBMS DVD.
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:
n For Windows Server 2003, double-click INSTMSI45.EXE
n 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 .Net
This procedure describes how to install SQL Server 2008, including the required Microsoft .Net Frameworks (if not already installed).
1. Double-click theSQL4SAP.VBSscript located in the root directory of your SQL Server 2008 RDBMS DVD.
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. We recommend that you do so as described above
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 DVD in 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 of publication) for an already existing SQL Server instance, enter the SQL Server instance name and choose OK.
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:
b) Restart theSQL4SAP.VBSscript.
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 that you choose Yes and update them.
Caution
Do not close the output console window, which shows all installation steps at all times. After the SQL4SAP window has closed, check theSQL4SAP.logfile, which is located in the WINDOWS directory. The log file contains all installation steps, return codes, and SQL commands.
Figure 6: Output Console Window
2 Additional Information
The SQL4SAP.VBS script installs Microsoft SQL Server in Windows Authentication mode. The script disables thesalogin and sets a random password for thesalogin. If you want to use thesalogin, you must change the authentication mode into SQL Server and Windows Authentication mode, enable thesa login and set its password, as described below.
Changing the Windows Authentication Mode into SQL Server and Windows Authentication Mode
To use SQL Server and Windows Authentication mode, you have the following options:
n You use the script_SqlAuth.vbs, which is located in the root directory on the RDBMS CD, to automatically install SQL Server 2008 with authentication mode SQL Server and Windows Authentication.
Note
A Java system requires the SQL Server and Windows Authentication mode.
n You manually change the authentication mode from Windows Authentication to SQL Server and Windows
Authentication 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 Authentication mode. 6. Choose OK.
Figure 8:Changing the Authentication Mode
Setting and Enabling the Password for the SQL Server Login sa
To set the password for thesalogin, 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 thesalogin. 6. Under Status, choose Login Enabled.
Figure 9:Setting a the Password for the SQL Server Login sa
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>”. Example
Example
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 Note123456
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, messages
n Source code or syntax quoted directly from a program
n 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,SELECTandINCLUDE
Germany T +49/18 05/34 34 34 F +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 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.
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, xApps, xApp, 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 in several other countries all over the world. 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.
Germany
T +49/18 05/34 34 34 F +49/18 05/34 34 20
