1774329 – Preparing your SAP instance to connect to remote SQL server

Home » Uncategorized » 1774329 – Preparing your SAP instance to connect to remote SQL server
September 10, 2014 Uncategorized No Comments
Symptom
*************************************************************
*   The following instructions apply to the Windows
*   operating environment.
*   If you are using Linux, then follow the instructions
*   of note 1644499.
****************************************************************

You want to configure an SAP application server instance to connect to a remote SQL Server using the DBCON database connectivity method.


Other Terms


Reason and Prerequisites
The application server must run on a Microsoft Windows Server operating system.


Solution
Obtaining the Required Software

If your SAP system is installed on Microsoft SQL Server, then your software is already installed.

The following section only applies when your SAP System is installed on a different database system than Microsoft SQL Server.

To create a connection from the SAP System to a SQL Server, you will need two database system-specific software components.  These are the Database Shared Library (DBSL) from SAP and the Microsoft SQL Server SNAC client library. You can download the SAP DBSL from SAP Service Marketplace.  The SNAC client can be downloaded from http://download.microsoft.com

You only have to set up the DBSL and the SNAC library once if your SAP System runs on a different database platform than SQL Server. Of course, you should also update both software products during your maintenance periods by following the same steps as the initial setup.
Downloading the DBSL from the Software Distribution Center on SAP Service Marketplace:

Open a Web browser and enter the following URL:
http://service.sap.com/swdc
In the navigation area, choose “Support Packages and Patches” and then “Browse our Download Catalog”.
In the navigation area, choose:
“SAP NetWeaver and complementary products”
-> “SAP NetWeaver”
-> <Choose your NetWeaver release>
-> “Entry by Component”
-> “Application Server ABAP”
-> <Choose the kernel release of your system>
-> “Windows Server <your platform>”
-> “MS SQL Server”
In the area “Download objects”, select the file “lib_dbsl_<patchlevel>-<nnnnnnnn>.sar”.
Make sure that you select the file with the highest patch level.
Download this file to a temporary folder.
To unpack the archive, use the program SAPCAR as follows:
SAPCAR -xvf lib_dbsl_<patchlevel>-<nnnnnnnn>.sar.
After you have successfully unpacked the archive, you no longer require the file lib_dbsl_<patchlevel>-<nnnnnnnn>.sar and you can delete it.

Downloading the MS SQL Server SNAC Client Software

Open a Web browser and enter the following URL:

http://download.microsoft.com

Normally you want to download SNAC client software which has a release which is equal or higher than the version of the SQL Servers you are connecting to. But in some cases the newest release can no longer connect to older SQL Servers.  For example the SQL 2012 SNAC client will not connect to SQL Server 2000.

Search on the words “Microsoft SQL Server Feature Pack”. Select the latest feature pack found, and scroll down to select the proper Microsoft SQL Server Native Client.  Download the proper sqlncli.msi for your platform.

The SQL Server 2008 client can connect to SQL Server 2008, SQL Server 2005 and SQL Server 2000 servers.

The SQL Server 2012 client can connect to SQL Server 2012, SQL Server 2008 and SQL Server 2005.

Installing the Software

The SNAC software is installed by running the sqlncli.msi file downloaded from the Microsoft website.

The DBSL dbmssslib.dll file is installed by moving it to the DIR_EXECUTABLE of your application server. You can check the location of this directory by running report RSPFPAR for example.  The current value for DIR_EXECUTABLE can be seen by choosing the row and pressing F2.
Updating the Client Software

When you install a SNAC client it has a release version tied to a specific SQL Server release. As you patch the SQL Server Database Engine with Microsoft Service Packs, you should also patch the SNAC Client.

For example, when you install the first release of SQL Server it is referred to as SQL Server 2012 RTM (“Release to Manufacturing”). The SNAC client installed at that time would also be the SQL Server 2012 SNAC RTM version. When you patch the database engine of SQL Server 2012 with Service Pack 1, you should also patch the SNAC client to SQL Server 2012 SNAC Service Pack 1 on any server which connects to the newly patched database.


Header Data
Released On 16.10.2012 20:40:20
Release Status Released for Customer
Component BC-DB-MSS Microsoft SQL Server
Priority Recommendations / Additional Info
Category FAQ


Validity

This document is not restricted to a software component or software component version 

References
This document refers to:

SAP Notes

1781460   Client unable to establish connection to SQL Server 2000
1644499   Database connectivity from Linux to SQL Server
1458291   SolMan 7.1 Database Warehouse & Alerting for MSSQL
1388700   SolMan 7.0 EHP1 Database Warehouse for MSSQL
1316740   Set up remote monitoring for Microsoft SQL Server databases
178949   MSSQL: Database MultiConnect
This document is referenced by:

SAP Notes (7)

178949   MSSQL: Database MultiConnect
1316740   Set up remote monitoring for Microsoft SQL Server databases
1458291   SolMan 7.1 Database Warehouse & Alerting for MSSQL
1388700   SolMan 7.0 EHP1 Database Warehouse for MSSQL
1644499   Database connectivity from Linux to SQL Server
1781460   Client unable to establish connection to SQL Server 2000
1954407   DBCON connections using Windows logins for SQL Server

LEAVE A COMMENT