First published on MSDN on May 08, 2017
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:
Due to the considerable number of customers moving off AIX/DB2 to Windows and SQL Server running on Azure a section of creating an R3load server for DB2 has been added
Migration of BW systems to SQL Server to leverage the Column Store, Flat Cube and FEMS pushdown logic continues to be popular with several major customers replacing SAP BWA with SQL Server Column Store
Post migration report RS_BW_POSTMIGRATION automatically converts F Fact and E Fact tables to Column Store when the recommended "All Column-Store" option is selected in SMIGR_CREATE_DDL
Windows 2016 is now Generally Available for almost all SAP applications on all major DB platforms other than Oracle 12c
Older Operating System and Database releases such as Windows 2012 (non-R2) and SQL 2012 are now no longer recommended for new projects
Ensure sp_updatestats is included in the post processing steps after the import
Many other recommendations around kernels, known bugs and Azure specific migration information
Recently a large Asian Airline recently moved from AIX/DB2 to Windows 2016 and SQL Server 2016 on Azure. The migration was completed in two phases over two weekends and was 100% successful with the customer realizing significant performance improvement running on D-Series VMs and Premium Storage.