Вы находитесь на странице: 1из 9

Installation Information

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

Document Version 1.20 – March 21, 2007


SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com

© Copyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP
or for any purpose without the express permission of SAP AG. The NetWeaver, and other SAP products and services
information contained herein may be changed without prior notice. mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in
Some software products marketed by SAP AG and its distributors contain Germany and in several other countries all over the world.
proprietary software components of other software vendors. All other product and service names mentioned are the
trademarks of their respective companies. Data contained
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks in this document serves informational purposes only.
of Microsoft Corporation. National product specifications may vary.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, These materials are subject to change without notice.
AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, These materials are provided by SAP AG and its affiliated
z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix companies ("SAP Group") for informational purposes
are trademarks or registered trademarks of IBM Corporation in the only, without representation or warranty of any kind, and
United States and/or other countries. SAP Group shall not be liable for errors or omissions with
respect to the materials. The only warranties for SAP
Oracle is a registered trademark of Oracle Corporation. Group products and services are those that are set forth in
the express warranty statements accompanying such
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open products and services, if any. Nothing herein should be
Group. construed as constituting an additional warranty.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, SAP Library document classification: PUBLIC
VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
Disclaimer
HTML, XML, XHTML and W3C are trademarks or registered Some components of this product are based on Java™.
trademarks of W3C®, World Wide Web Consortium, Massachusetts Any code change in these components may cause
Institute of Technology. unpredictable and severe malfunctions and is therefore
expressively prohibited, as is any decompilation of these
Java is a registered trademark of Sun Microsystems, Inc. components.

JavaScript is a registered trademark of Sun Microsystems, Inc., used Any Java™ Source Code delivered with this product is
under license for technology invented and implemented by Netscape. only to be used by SAP’s Support Services and may not
be modified or altered in any way.
MaxDB is a trademark of MySQL AB, Sweden.
Typographic Conventions Icons

Type Style Represents Icon Meaning


Example Text Words or characters that appear Caution
on the screen. These include
field names, screen titles, Example
pushbuttons as well as menu
names, paths and options.
Note
Cross-references to other
documentation Recommendation
Example text Emphasized words or phrases in
body text, titles of graphics and Syntax
tables
EXAMPLE TEXT Names of elements in the
system. These include report
names, program names,
transaction codes, table names,
and individual key words of a
programming language, when
surrounded by body text, for
example, SELECT and
INCLUDE.
Example text Screen output. This includes file
and directory names and their
paths, messages, names of
variables and parameters,
source code as well as names of
installation, upgrade and
database tools.
Example text Exact user entry. These are
words or characters that you
enter in the system exactly as
they appear in the
documentation.
<Example text> Variable user entry. Pointed
brackets indicate that you
replace these words and
characters with appropriate
entries.
EXAMPLE TEXT Keys on the keyboard, for
example, function keys (such as
F2) or the ENTER key.
Installation Information

Customized Installation of SQL Server 2005


for an SAP System with SQL4SAP.VBS
Use
This documentation explains how to use the SQL4SAP.VBS script to install SQL Server 2005 for your SAP
system. For up-to-date information on the installation of SQL Server 2005 with SQL4SAP, read SAP Note
896566.

The SQL4SAP.VBS script does not support Microsoft Cluster Service (MSCS). For more
information about how to install your SQL Server database software for MSCS, see the
installation guide for MS SQL Server.
Features
With the SQL4SAP.VBS script you can install:
One of the following SQL Server 2005 editions:
32-bit SQL Server 2005 Enterprise Edition on x86 systems
64-bit SQL Server 2005 Enterprise Edition on x64 systems
64-bit SQL Server 2005 Enterprise Edition on IA64 systems

With SQL4SAP.VBS you can install 32-bit and 64-bit editions of SQL Server 2005 on various
Windows operating systems. Not all combinations of SQL Server and Windows are supported
by all SAP products. For more information, see the Product Availability Matrix (PAM) on SAP
Service Marketplace at: service.sap.com/platforms Product Availability Matrix
The latest SQL Server 2005 service pack

You can use the SQL4SAP.VBS script to upgrade your SQL Server 2005 to the latest service
pack, however you cannot use it to upgrade from SQL Server 2000 to SQL Server 2005.
Default Instances, Named Instances, or SQL Server Client Tools Only
Prerequisites
You use one of the following Windows operating systems:
Windows Server 2003
Windows Server 2003 for 64-bit Itanium-based systems
Windows Server 2003 x64 Edition
Future Windows Server (codename Longhorn)

To install SQL Server Client Tools Only for monitoring your SAP system, you can also use
Windows XP and Windows Vista.

Procedure
1. Log on as an administrator
2. Double-click the SQL4SAP.VBS script located in the root directory of your SQL Server 2005
RDBMS DVD.

4 March 2007
Installation Information

An output console window appears that shows all installation steps at all time.

In Windows Vista and future Windows versions a User Account Control Window might occur.

3. In the Select SQL Server Instance window, do one of the following:


To install a Default Instance, choose OK.
SAP recommends that you install a default instance.
To install a Named Instance, SAP recommends that you enter the same name that you used for
your SAP system ID (SAPSID).
To install the SQL Server Client Tools Only software, choose Cancel.

This option is not available if the SQL Server Client Tools Only software is already
installed.
The SQL Server Client Tools Only software is not required for an SAP application
server. Install the SQL Server Native Client (SNAC) instead by double-clicking the
sqlncli.msi file. You find the file in the platform-specific directory of the SQL Server
2005 RDBMS DVD.

To install the latest service pack for an already existing SQL Server instance, enter the SQL
Server instance name and choose OK.

March 2007 5
Installation Information

4. In the Confirmation window check your entries and choose OK to start the SQL Server installation,
or the upgrade to the latest service pack as shown in the following graphics:

Confirmation window for SQL Server 2005 installation

Confirmation window for upgrade to the latest SQL Server 2005 service pack

The output console window shows all installation steps (installation of SQL Server and the service
pack) at all times.
The installation may take several minutes.

Do not close the output console window. 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.

6 March 2007
Installation Information

5. If the installation was successful, the Installation finished successfully window appears.

Additional Information
Changing the Windows Authentication Mode
The SQL4SAP.VBS script installs Microsoft SQL Server in Windows Authentication mode and sets a random
password for the sa login. If you want to use the sa login, you must change the authentication mode to SQL
Server and Windows Authentication mode, enable the sa login and set its password.
You can also use the script _SqlAuth.vbs on the CD, if you want to install authentication mode to SQL
Server and Windows Authentication automatically.

Currently a Java system requires the SQL Server and Windows Authentication mode.
To change the authentication mode from Windows Authentication to SQL Server and Windows
Authentication, manually use the SQL Server Management Studio as follows:
1. Choose All Programs Microsoft SQL Server 2005 SQL Server Management Studio.

March 2007 7
Installation Information

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.

Setting and Enabling the Password for the SQL Server Login sa
To set the password for the sa login, you use the SQL Server Management Studio:
1. Choose All Programs Microsoft SQL Server 2005 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.

8 March 2007
Installation Information

7. Choose OK.

March 2007 9

Оценить