Supported SQL Server Version for SAP NetWeaver 7.4 SR2 NEW !

Note that for SAP NetWeaver 7.4 SR2 (SAP NetWeaver 7.4 SP8)  only SQL Server 2012 is supported. 21 Oct 2014

Analyzing Network Errors on SQL Server

SAP application servers occasionally lose connections to the SQL Server database server. This paper discusses how to approach the problem of solving intermittent connection loss, and some common causes of connection problems. Important SAP notes and the preferred problem-solving approach are identified. 19 Feb 2014

SQL Server 2012 Column-Store Available For All Major SAP BW Releases

SQL Server 2012 introduced a new storage format for data. Besides the traditional row-oriented store, there is now also a column-oriented store available. The column-oriented store is optimized for aggregating mass data, while the row-oriented store can be optimally used when accessing just a single row. SQL Server 2012 column-store support has been integrated into all major SAP BW releases. You can now benefit from increased query performance and reduced disk space requirements. 05 Nov 2012

SAP Database Performance Warehouse for SQL Server in Solution Manager 7.1

The SAP Database Performance Warehouse (DPW) contains key database performance indicators of your SAP system landscape for status reporting and long term performance analysis. It is used by the Solution Manager Diagnostics (SMD) back-end and is therefore an integrated part of SAP Solution Manager. For information about SAP DPW for the previous SAP Solution Manager version 7.0 EHP1, see the following presentation.  26 Jan 2012

Immense Disk Space Savings with SQL Server

Database compression dramatically reduces the disk space needed for an SAP NetWeaver system running on SQL Server. As of SQL Server 2008 R2, this uses an improved encoding algorithm for Unicode, also known as Unicode-compression. This results in less storage requirements for SAP Unicode systems. For more information, see this blog. In May 2011, SAP changed the default compression type from ROW to PAGE compression, which led to an additional reduction in the database size. For more information, see this document. 22 Sep 2011

The DBA Cockpit and Microsoft SQL Server

The DBA Cockpit is a powerful feature for SAP NetWeaver applications. The following presentations provide tips and advice on how system administrators can use the DBA Cockpit for local monitoring and analysis of Microsoft SQL Server systems. Each presentation includes a PowerPoint with audible narration.

• SAP DBA Cockpit and Microsoft SQL Server
• SAP DBA Cockpit and Microsoft SQL Server - Real Time Performance Analysis
• System Administration for SAP and SQL Server with DBA Cockpit
• SAP DBA Cockpit and Microsoft SQL Server - Historic Performance Analysis

31 Aug 2011

See more recently featured content

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on April 2015.

BC-DB-MSS*

BW-SYS-DB-MSS

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

The purpose of this document is to provide a location list of the installation guides for SQL Server Netweaver based products and notes.

Guides

https://service.sap.com/instguides

• Database Upgrades
  • MS SQL Server
    • Upgrade to and Installation of SQL Server 2000
    • Upgrade to and Installation of SQL Server 2005
    • Upgrade to and Installation of SQL Server 2008 (R2)
    • Upgrade to and Installation of SQL Server 2012
    • Upgrade to and Installation of SQL Server 2014

Notes

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

The purpose of this document is to clarify about the access to the download media of SQL Server.

New General Download Restrictions for all SQL Server Releases:

As of April 2015, downloading the SQL Server installation media for NetWeaver based systems from the SAP Service Market Place is restricted to SAP customers who have licensed Microsoft SQL Server through SAP. SAP customers who have acquired their SQL Server license from Microsoft or a re-seller, needs to obtain the installation media from Microsoft or the re-seller.

SQL Server 2014 Download Restrictions:

As of SQL Server 2014, Microsoft has included new Use Terms in the licenses sold under the reselling agreement with SAP. As a re-seller, we must notify customers of the new Use Terms and we must receive acknowledgement of the customers' receipt of the terms. Therefore, all customers who have purchased their SQL Server license from SAP must contact their SAP Account Executive (or SAP Partner/Re-seller) in order to obtain a copy of the new use terms via an Amendment and sign their receipt of the Amendment. If you have not signed the agreement you will not be able to see the SQL Server 2014 in the download area of SAP Service Marketplace!

Regarding the new Use Terms, see SAP Note 2139358 for more details on the change. Once you have returned the signed Amendment, SAP will enable download of SQL Server 2014 and subsequent editions for your installations.

SAP Notes about Installation Media:

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on May/June 2015.

BC-DB-MSS*

BC-DB-MSS-CCM*

BW-SYS-DB-MSS*

KBAs/Notes that belongs to other components but are related to SAP NetWeaver on SQL Server:

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

The Following steps describes how to increase the DATAFILE size if there is no space left in each file and the status of the each DATAFILE showing RED color in DB02 Transaction

Step1: Check the available space from transaction DB02

Space Overview Screen

Goto Files Tab -> Free Space in Disk

If there is enough space available we can increase the space from the same drive

Also check the existing free space left for each file , If the Exception  Column in Database Files tab showing RED there is no free space left

If its Green there is some space exists

Step 2: If there is no free space and the Exception Column showing RED , We need to increase the space

To do this goto transaction DB02 -> Diagnostics -> SQL Command Editor from SAP

and execute the following command

ALTER DATABASE <SID> MODIFY FILE (NAME = '<SID>DATA2',SIZE = 6144)

Here SIZE in MBs and should be greater than existing files size

Do this for remaining all the DATA Files and make sure the free space should be greater than 10 % overall.

Taking transaction log backup from SAP Gui Using SQL Query from Sql Command Editor

Use the following Query to take Transaction log backup using Sql Command Editor in to a DISK

BACKUP LOG <SID> TO DISK = ‘D:\<FILENAME>.TRN

Thanks,

Chandrababu

This document is about upgrading from SQLServer 2008R2 to SQLServer 2012.

Useful docs to perform the operation :

SAP notes :

     1676665 - Setting up Microsoft SQL Server 2012

     1651862 - Release planning for Microsoft SQL Server 2012

     1684545 - SAP Installation Media and SQL4SAP for SQL Server 2012

Installation and upgrade guide :

The SQLServer upgrade and installation guide for SAP is also highly useful.

Located here :

http://service.sap.com/instguides -> Database Upgrades -> MS SQL Server

     Upgrade to and Installation of SQL Server 2012 in an SAP Environment

Starting point :

I'm currently running SQLServer 2008R2 SP3.

These are my system information :

You have to pay attention to the SAP release / SPS level you are running. This has to be compatible with the target SQLServer release.

Also, you have to pay attention to your SAP kernel release. The target kernel release has to be compatible with your target SQLServer Version.

In general, before performing the DB upgrade, at least the SAP kernel update should be done.

The SQLServer upgrade process:

It mainly consists of 2 phases.

1 you perform the update using the SQLServer media.

2 you perform the post update tasks for SAP using the SWPM.

Example :

Now , provided all the pre requisites are satisfied in terrms of SAP application / kernel releases, you can perform the update  :

Stop SAP.

Stop the SQLServer db services.

--> Do it as usual using the SAP MMC to stop the SAP Instance and also stop any SAP and SQLserver related services.

Once you have downloaded and extracted the SQLserver medium ( Here it was 51047515 media DVD ) , run the update

Start the upgrade using setup.exe :

F:\SQLSERVER2012\51047515\x86-x64\EnterpriseEdition\setup.exe

And we have performed the following choices :

In the above screen, you have nothing to provide. The product key  is there by default.

Highlight from Matt's comment about the license key :

One thing to note, however, is that the SQL Server product key is only there by default if you are using installation media provided by SAP as part of a runtime license. Not every customer obtains their SQL Server license from SAP -- some buy it directly from Microsoft -- and so in that case this field is not pre-populated.

You accept the license agreement.

In the next screen, you choose the instance to upgrade.

The choices will be done by default, based on the installed features :

You validate this screen.

You validate this screen.

You validate this screen.

We kept here the default choice:

We kept here the default choice here also :

With this last screen we are ready to upgrade :

And then the upgrade runs :

Once done, you'll have these summary screens. you'll need to restart the Server :

Now the process is completed and the system restarted you can proceed with the second phase using the SWPM to perform the SAP post upgarde steps :

Let' s run the SWPM to finalize the upgrade :

We performed the following choices :

Generic Installation Options -> MS SQL Server -> Database upgrade Completion :

Once it is completed you get this screen :

Nothing much to say about it as this part of the process is usually smooth and fast.

Before giving the system back you update the stats :

And set this option.

You can  then restart your SAP instance and perform some quick checks.

And there it is. You' re now running SQLServer 2012.

Should you have external Application servers connecting to the DB server you'll have to update the SQLServer client software using the corresponding SNAC package.

You'll also have to check the SQLServer agnt parameters on the DB server as described in the SQLServer installation / update guide.

And then you're done !