Browse by Tags

SAP BW query performance depends on many factors: hardware, database configuration, BW configuration and last but not least BW cube design and BW query design. When running a query, there are several caches involved: disk caches, database caches and the BW OLAP cache. You should keep this in mind when...

SQL Server column-store is generally supported by SAP BW since end of October 2012. One of the prerequisites is importing the correction instructions of SAP note 1771177 . Last week we published a new version of this note with additional improvements. We recommend to update your SAP BW code by applying...

Last Week SAP released Support Package Stack 5 for EHP1 of NetWeaver 7.3. Hereby all of the following equivalent SPS levels are now available: SPS 27 of SAP BW 7.0 (SAP NetWeaver 7.0) SPS 12 of SAP BW 7.01 (SAP enhancement package 1 for SAP NetWeaver 7.0) SPS 12 of SAP BW 7.02 (SAP enhancement...

In the following we explain, how database statistics should be updated for SAP BW running on Microsoft Server. In particular, we describe the new feature “Lightweight Update Statistics”, which speeds up by factors SAP BW process chains containing Update Statistics. The implementation of...

The latest SAP support packages contain a bunch of improvements for SAP BW running on Microsoft SQL Server. The improvements can be assigned to two areas: Support for SQL Server 2012 column-store. We will describe this in detail in a separate BLOG. An overview can be found at http://blogs.msdn...

SQL Server 2012 introduced an additional storage format for data. Besides the normal row-oriented store, there is a column-oriented store as well (like in SAP HANA). In order to make it as transparent as possible, the new column store got exposed to the Database Administrators and Applications as a new...

The cost based query optimizer of SQL Server relies on actual index and column statistics. SAP strongly recommends setting the database options AUTO_UPDATE_STATISTICS and AUTO_CREATE_STATISTICS. As a result, statistics are automatically maintained. We recently described the details in the following BLOG...

The creation of database indexes is often a significant part in SAP BW process chains. Even on up-to-date database servers the index creation on a BW cube may take several hours. The obvious way to speed-up this procedure would be to increase parallelism by setting the SQL Server configuration option...

SAP encourages their customers to convert existing non-Unicode systems to Unicode. However, several SQL Server customers hesitated to perform a Unicode Conversion, because of the increased storage requirements of UCS-2. This issue has been finally solved with Unicode-compression, which is a new feature...

SAP supports SQL Server Data Compression (row- and page-compression) for all applications based on ABAP application server as of NetWeaver (NW) Basis 7.00 and SQL Server 2008. Per default, SAP used to create tables with compression type ROW and indexes with compression type NONE. This decision was made...

As of SQL Server 2005 you can partition table and indexes. The maximum number of partitions used to be 1,000 for SQL Server 2005, 2008 and 2008 R2. Some customers were reaching this limit when running SAP Business Warehouse (SAP BW) on Microsoft SQL Server. Therefore it was decided to increase this limit...

1. the issue In 2009 Microsoft certified the Microsoft Connector 1.1 for extracting data from SAP BW 7.x via the Open Hub Service API : The SSIS connector for SAP BW is for free but has to be downloaded from the SQL Server "feature pack". Here is a link to the 2008 R2 feature pack : http...

1. the issue and how it was handled in the past The issue and how it was handled in the past is already described in my last blog where I showed how SQL Server Reporting Services 2008 R2 can be used to solve the problem : SSRS 2008 R2 - a new way of MS BI integration .....   2. how the issue could...

  1. the issue In customer scenarios with the requirement to integrate data out of SAP BW with some non-SAP data sources people usually recommended to first consolidate and load everything into a single system ( either SAP BW or SQL Server/SSAS ). Any kind of reporting or data analysis would then...

SAP released the report MSSCOMPRESS in SAP note 1488135. The report can be used to compress existing tables and indexes using the data compression feature of SQL Server 2008 (and all newer releases). You can choose between the compression type NONE, ROW or PAGE for the data (heap or clustered index)...

Depending on the SAP and SQL Server release, there are different compression types supported by SAP NetWeaver. Unfortunately the naming convention used by SAP and Microsoft is not consistent. Therefore there was some confusion about this in the past. In SAP notes the following compression types are mentioned...

Welcome Hermann Daeubler on this blog site. Hermann is Program Manager in SQL Server Development and our specialist for SAP BW and integration of Microsoft products into SAP BW. Hermann is part of our onsite team in the SAP Netweaver Development in Germany Scenario: The most important advantage of table...