Sql4sap Docu

5/20/2018 Sql4sap Docu

1/20

Installation Guide

Customized Installation of SQL Server 2012 for an SAP System

with SQL4SAP

Target Audience

Technology Consultants

System Administrators

CUSTOMERDocument version: 1.10 2013-01-14


2/20

Document History

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

Version Date Description

1.10 2013-01-14 Updated VersionContains Windows Server 2012 information

1.00 2012-03-22 Initial Version

2/20 CUSTOMER 2013-01-14


3/20

Table of Contents

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

SQL4SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 Installing SQL Server 2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

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

2.1 Changing the Windows Authentication Mode into SQL Server and WindowsAuthentication Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

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

2013-01-14 CUSTOMER 3/20


4/20

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


5/20

1 Customized Installation of SQL Server2012 for an SAP System with SQL4SAP

This documentation explains how to use the SQL4SAP script to install SQL Server 2012 for your SAP

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

1684545.

CAUTION

The SQL4SAP 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-availability

system, see the installation guide for MS SQL Server.

Features

With the SQL4SAP script you can install:

One of the following SQL Server 2012 editions:

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

64-bit SQL Server 2012 Enterprise Edition on x64 systems

CAUTION

SAP does not support the 32-bit edition of SQL Server 2012.

SAP does not support SQL Server 2012 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 2012 service pack, or cumulative update (if available)

CAUTION

You cannotuse the SQL4SAP script to upgrade SQL Server 2000, SQL Server 2005 or SQL

Server 2008 (R2) to SQL Server 2012. Default Instances, Named Instances, or SQL Server Client Toolsonly, or SQL Server Native Access Tools

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 followingUser Account Controlwindow might

appear:

1 Customized Installation of SQL Server 2012 for an SAP System with SQL4SAP

2013-01-14 CUSTOMER 5/20
http://service.sap.com/platformshttp://service.sap.com/platformshttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1684545&_NLANG=en&_NVERS=0


6/20

Figure 1: User Account Control Window

Prerequisites

You use one of the following 64-bit Windows operating systems:

Windows Server 2008 Editions:

Windows Server 2008 Standard Edition with Service Pack 2

Windows Server 2008 Enterprise Edition with Service Pack 2

Windows Server 2008 Datacenter Edition with Service Pack 2

Windows Server 2008 R2 Editions:

Windows Server 2008 R2 Standard Edition with Service Pack 1

Windows Server 2008 R2 Enterprise Edition with Service Pack 1

Windows Server 2008 R2 Datacenter Edition with Service Pack 1 Windows Server 2012 Editions:

Windows Server 2012 Standard Edition

Windows Server 2012 Datacenter Edition

For more information about the prerequisites for SQL Server 2012 see:

http://msdn.microsoft.com/en-us/library/ms143506(v=sql.110).aspx

1.1 Installing SQL Server 2012

This procedure describes how to install SQL Server 2012 with the SQL4SAP.BAT script. The script also

installs required additional software for example, the .NET Framework 3.5 SP1 patch, or Powershell

2.0.

Procedure

1. Run the SQL4SAP.BAT script from an elevated command prompt.

The script is located in the root directory of your SQL Server 2012 RDBMS DVD provided by SAP.

If the .NET Framework 3.5.1 is not yet installed on your system, the script installs or enables it.

NOTE

For Windows Server 2012, you have to enable .NET 3.5 manually as described at:



6/20 CUSTOMER 2013-01-14
http://msdn.microsoft.com/en-us/library/ms143506%28v=sql.110%29.aspxhttp://msdn.microsoft.com/en-us/library/ms143506%28v=sql.110%29.aspx


7/20

http://technet.microsoft.com/en-us/library/hh831809.aspx#BKMK_FoD.

Figure 2: .NET Framework 3.5.1 Installation

2. If you started the script from a network share, a security dialog might appear.

To continue, choose Run.

Figure 3: Security Warning

3. If you use Windows Server 2008, the following dialog appears during the installation of .NET

Framework 3.5.1:

Figure 4: .NET Framework 3.5.1 Installation Progress

4. Choose your installation type.


1.1 Install ing SQL Server 2012

2013-01-14 CUSTOMER 7/20
http://technet.microsoft.com/en-us/library/hh831809.aspx#BKMK_FoD


8/20

1. To install SQL Server 2012 (default), press Enter.

2. To install the SQL Server Client Toolssoftware for monitoring your SAP system, type 2and then

press Enter.

3. To install the SQL Server Native Client (SNAC)software for monitoring your SAP system, type

3and then press Enter.

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

2012 RDBMS DVD in the directory: :\SqlNativeClient\\

For more information, see SAP Note 1684545.

Figure 5: Installation Type to Choose

5. If you have chosen the first option SQL Server installation, SQL4SAP asks you to enter the name of the

SQL Server instance.

To install a default instance (recommended), press Enter.

Figure 6: Instance Name



8/20 CUSTOMER 2013-01-14
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1684545&_NLANG=en&_NVERS=0


9/20

6. By default, SQL4SAP adds the BUILTIN\Administratorsgroup to the SQL Server logins.

If you wish to add a different user, enter the name and press Enter.

Figure 7: User Name for the sysadmin Login

7. If required, the SQL4SAP script installs additional software, for example the .NET Framework 3.5

SP1 patch, or Powershell 2.0.

Figure 8: Additional Software

8. If required, restart your system after the installation of the additional software.



2013-01-14 CUSTOMER 9/20


10/20

Figure 9: Restart Required

9. After you have restarted your system, restart SQL4SAP and continue with the installation.

CAUTION

Do not close the output console window, which shows all installation steps at all times.

Figure 10: SQL Server 2012 Installation

10. When the installation is finished, restart your system.



10/20 CUSTOMER 2013-01-14


11/20

Figure 11: Installation Finished Successfully

11. After the SQL4SAP window has closed, check the SQL4SAP.logfile, which is located in the

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



2013-01-14 CUSTOMER 11/20


12/20

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


13/20

2 Additional Information

The SQL4SAP.bat script installs Microsoft SQL Server in Windows Authenticationmode. The script disables

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

change the authentication mode into SQL Server and Windows Authenticationmode, enable the salogin and

set its password, as described below.

2.1 Changing the Windows Authentication Mode into SQLServer and Windows Authentication Mode

Procedure

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

You use the script _SqlAuth.bat, which is located in the root directory on the RDBMS DVD, to

automatically install SQL Server 2012 with authentication mode SQL Server and Windows

Authentication.

NOTE

A Java system requires theSQL Server and Windows Authentication

mode. You manually change the authentication mode Windows Authenticationto SQL Server and Windows

Authenticationin the SQL Server Management Studio as follows:

1. Choose All Programs Microsoft SQL Server 2012 SQL Server Management Studio .

2. In the Connect to Serverwindow, 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, chooseSQL Server and Windows Authenticationmode.

6. Choose OK.

7. Restart SQL Server.


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

2013-01-14 CUSTOMER 13/20


14/20

Figure 12: Changing the Authentication Mode

2.2 Setting and Enabling the Password for the SQL ServerLogin sa

Procedure

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

1. Choose All Programs Microsoft SQL Server 2012 SQL Server Management Studio .

2. In the Connect toServerwindow, enter the server name (if required), and choose Connect.

3. Choosethe SQL Server instance Security Logins .

4. Right-click saand choose Properties.

5. Under General, enter and confirm the password for the salogin.

6. Under Status, choose Login Enabled.

7. Choose OK.


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

14/20 CUSTOMER 2013-01-14


15/20

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

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


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

2013-01-14 CUSTOMER 15/20


16/20

Typographic Conventions

Example Description

Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, Enter your .

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

documentationhttp://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, andnames 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, SELECTand INCLUDE

EXAMPLE Keys on the keyboard

16/20 CUSTOMER 2013-01-14
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0http://www.sap.com/


17/20

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34

F +49/18 05/34 34 20www.sap.com

Copyright 2013 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, PowerPoint, Silverlight, and Visual Studio are registered trademarks of MicrosoftCorporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/

OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,

pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,

OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of

IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems

Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

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.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are

trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm,

BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research

in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile

Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik

and Android are trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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. Business Objects is an SAP company.

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.

2013-01-14 CUSTOMER 17/20


18/20

Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other

countries. Crossgate 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.

Disclaimer

Some 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 SAPs Support Services and may not be modified or

altered in any way.

18/20 CUSTOMER 2013-01-14


19/20


20/20

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

Copyright 2013 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 containedherein may be changed without prior notice.

Documents

Sql4sap Docu