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 :

Source sys char1.png

Source sys char2.png

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


sqlserver upgrade1.png


And we have performed the following choices :

sqlserver upgrade2.png


sqlserver upgrade3.png

sqlserver upgrade4.png


sqlserver upgrade5.png


sqlserver upgrade7.png

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.

sqlserver upgrade8.png

You accept the license agreement.

sqlserver upgrade9.png

sqlserver upgrade10.png

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

sqlserver upgrade11.png

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

sqlserver upgrade12.png

You validate this screen.

sqlserver upgrade13.png

You validate this screen.

sqlserver upgrade14.png

You validate this screen.

sqlserver upgrade15.png

We kept here the default choice:

sqlserver upgrade16.png

We kept here the default choice here also :

sqlserver upgrade17.png

sqlserver upgrade18.png

With this last screen we are ready to upgrade :

sqlserver upgrade19.png

And then the upgrade runs :

sqlserver upgrade20.png

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

sqlserver upgrade21.png

sqlserver upgrade22.png

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 :

sqlserver upgrade23.png

sqlserver upgrade24.png

Once it is completed you get this screen :

sqlserver upgrade25.png

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 :

sqlserver upgrade26.png

And set this option.

sqlserver upgrade27.png

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

sqlserver upgrade28.png

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 !




To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

  1. Matt Fraser

    Hi Steve,

    Nice summary of the process. 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.

    More to the point, though, that license key, clearly shown in your screenshot, is only for use with the SAP runtime-licensed version of SQL Server. It will work in any SQL Server distribution, but for anyone else to use it who didn’t buy their license from SAP, that would be a violation. Therefore, I think you should edit that screenshot to blank out the license key, as otherwise you are essentially “giving away” the license to the product to anyone on the Internet who finds this blog.

    Cheers,

    Matt

    (0) 
      1. Luis Darui

        Hi Matt,

        Thanks for highlight this. I didn’t have time to read all the document when it was released and when I saw a comment I edited the document, but this needs to go into moderation review now.

        Regards, Luis

        (0) 
        1. Steve Soumah Post author

          Hi Luis,

          I didn’t realize I had left the key in the screenshot.

          I’ve edited it. It’s O.K now.

          Thanks Luis and best regards,

          Steve.

          (0) 
    1. Steve Soumah Post author

      Thanks Matt for the precision around the license key.

      I forgot to blank the screenshot also. This is done now.

      I’ve added your comment in the document.

      Thanks and Best regards,

      Steve.

      (0) 
  2. Raj Rathnam

    Steve, After the SQL Server is upgraded, one MUST perform the post -processing steps as explained in SAP Note#683447 before they start the SAP system. Regards, Raj

    (0) 
    1. Steve Soumah Post author

      Hello Raj,

      You are right and these are the points I mention under :

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

      And also after :

      Let’ s run the SWPM to finalize the upgrade

      The “Database upgade completion” from SWPM right ?

      (0) 

Leave a Reply