- First published on MSDN on Jan 08, 2015 by Martin Merdes.
- This blog post might be outdated by now. The latest documentation regarding SQL Server Columnstore on SAP is available in https://www.sap.com/documents/2019/04/023e5928-487d-0010-87a3-c30de2ffd8ff.html and in https://launchpad.support.sap.com/#/notes/2116639
- The performance impact of SQL Server Columnstore is described in https://techcommunity.microsoft.com/t5/Running-SAP-Applications-on-the/Performance-evolution-of-SAP-BW-on-SQL-Server/ba-p/368073
This blog was originally released in January 2015. It contained the text of https://service.sap.com/sap/support/notes/2114876 . In the meanwhile, the recommendations in this SAP note have changed a few times. Therefore, I removed the outdated information from this blog today (Mai 2017). Read the SAP Note instead.
However, I still want to share the following information from https://service.sap.com/sap/support/notes/2114876 here:
Minimum, recommended code for Columnstore
To benefit from most improvements, it is highly recommended (as at November 2016) to apply at least the following SAP Support Package Stacks (SPS)
| SAP release | 7.00 | 7.01 | 7.02 | 7.11 | 7.30 | 7.31 | 7.40 | 7.50 |
| SAP SPS | 32 ** | 17 | 17 | 15 | 13 | 15 | 13 | 4 |
| ** | In SAP NetWeaver 7.00 , the number of the SAP BW SP is always 2 numbers higher than the number of the SPS. For example, SAP NetWeaver SPS 32 contains SAP_BASIS SP 32, but SAP_BW SP 34 . |
Updated May 10, 2019
Version 4.0