SAP OS/DB Migration to SQL Server–FAQ v6.1 November 2016
Published Mar 13 2019 10:43 AM 208 Views
First published on MSDN on Nov 24, 2016
The FAQ document attached to this blog is the cumulative knowledge gained from hundreds of customers that have moved off UNIX/Oracle and DB2 to Windows and SQL Server in recent years.
In this document a large number of recommendations, tools, tips and common errors are documented.  It is recommended to read this document before performing an OS/DB migration to Windows + SQL Server.

The latest version of the OS/DB Migration FAQ includes some updates including:

  1. Customers are increasingly moving large SAP systems in the 5-10TB range to Azure.  This press release is an example of one of many successful projects

  2. With powerful new VMs, Accelerated Networking and Premium Storage it is now possible to import even huge size SAP databases on Azure

  3. Based on experience from recent migrations we recommend using SQL Server 2014 SP2 CU2 or SQL 2016 SP1 (as at November 2016).  It is generally recommended to use the latest Service Pack and Cumulative update

  4. A future blog will cover specific recommendations for BW migrations.  Some changes have been made to improve import performance on BW fact tables and other general recommendations.  These will appear in a blog shortly

  5. Intel has released both the E5v4 and E7v4 processors.  2 socket commodity Intel servers now benchmark ~120,000 SAPS and 4 socket Intel servers now benchmark ~220,000 SAPS

  6. Customers still running on UNIX platforms are terminating these platforms and moving to more cost effective Intel systems with much better performance

  7. Multiple customers have terminated the use of SAP BW Accelerator and replaced this with SQL Server's built in Column Store.  The OS/DB Migration FAQ now includes a link to the procedure to remove BWA configuration from a BW system

Latest OS/DB Migration FAQ can be downloaded from the link below

Version history
Last update:
‎Mar 13 2019 10:43 AM
Updated by: