SAP NetWeaver Newbie

Three solutions from SAP Analytics portfolio

OpenSAP has announced some new courses on SAP BusinessObjects Cloud and SAP Digital Boardroom powered by SAP BusinessObjects Cloud.

SAP Analytics - BusinessObjects


While I am yet to learn about SAP BusinessObjects Enterprise, prospects of learning these new solutions created some confusion. So I took it upon myself to find out what these products are all about.

SAP has been branding its products on analytics around BusinessObjects. BO has been a known brand name in analytics, so why rename and spoil that brand. Naturally BO is the name to go after.

The on-premise solutions for analytics are delivered as SAP BusinessObjects Enterprise. This product is available in three variants: Premium, Professional and Standard; in the decreasing order of functionalities delivered.

Given the push for software-as-a-service or on-cloud products, SAP has introduced a cloud variant of BOE. They call it SAP BusinessObjects Cloud. They originally called it  SAP Cloud for Analytics, but stuck to the naming theme of the brand BO.

SAP Digital Boardroom (powered by SAP BusinessObjects Cloud) extends SAP BusinessObjects Cloud with support for live-meetings and collabaration aspects. This is meant for use by executive management team and board of directors of a company.

I suppose the openSAP courses will shed more light on these new products and hopefully I can leverage the basic knowledge from BOE to understand what they are.

Reorganising database reduces IO load by a huge factor

Today I learned that an IO bottleneck in Oracle can be reduced significantly if the database is reorganized.

Reorganizing the DB reduces IO by a huge factor

We had a problem with a badly designed database file layout.

SAP application, Oracle data files and the redo logs were all configured to be stored on a single disk.

A higher than normal load on SAP system caused the entire system to crawl. Quickly checking a few transactions, which included ST06, showed that the response time of disks was very high, more than 500 ms.

Before planning to redistribute the data files and redo logs away to a new disk, someone wanted to try a DB reorganization. When you reorganize the database, the fragmentation of data is reduced. So a read requires fewer blocks to be read and thus reduces the load on the disk.

After the DB was reorged, problem was gone!

Microsoft Windows and SQL Server Versions


Unless you are good with remembering numbers, you can't just look at the version number information of MS Windows or MS SQL Server and tell what the release, SP levels etc are.

To quickly establish a correlation, you can use these two resources:

Operating System Version (Windows)
Microsoft SQL Server Version List

For a quick reference, I have copied the latest information here:

Operating systemVersion number
Windows 1010.0*
Windows Server 2016 Technical Preview10.0*
Windows 8.16.3*
Windows Server 2012 R26.3*
Windows 86.2
Windows Server 20126.2
Windows 76.1
Windows Server 2008 R26.1
Windows Server 20086
Windows Vista6
Windows Server 2003 R25.2
Windows Server 20035.2
Windows XP 64-Bit Edition5.2
Windows XP5.1
Windows 20005

* For applications that have been manifested for Windows 8.1 or Windows 10. Applications not manifested for Windows 8.1 or Windows 10 will return the Windows 8 OS version value (6.2).

RTM (no SP)SP1SP2SP3SP4
↓ SQL Server 2016
     codename ?
13.0.1601.5
↓ SQL Server 2014
     codename Hekaton SQL14
12.0.2000.812.0.4100.1
or 12.1.4100.1
↓ SQL Server 2012
     codename Denali
11.0.2100.6011.0.3000.0
or 11.1.3000.0
11.0.5058.0
or 11.2.5058.0
11.0.6020.0
or 11.3.6020.0
↓ SQL Server 2008 R2
     codename Kilimanjaro
10.50.1600.110.50.2500.0
or 10.51.2500.0
10.50.4000.0
or 10.52.4000.0
10.50.6000.34
or 10.53.6000.34
↓ SQL Server 2008
     codename Katmai
10.0.1600.2210.0.2531.0
or 10.1.2531.0
10.0.4000.0
or 10.2.4000.0
10.0.5500.0
or 10.3.5500.0
10.0.6000.29
or 10.4.6000.29
↓ SQL Server 2005
     codename Yukon
9.0.1399.069.0.20479.0.30429.0.40359.0.5000
↓ SQL Server 2000
     codename Shiloh
8.0.1948.0.3848.0.5328.0.7608.0.2039
↓ SQL Server 7.0
     codename Sphinx
7.0.6237.0.6997.0.8427.0.9617.0.1063

Near line Storage in SAP BW

Today I learned that apart from archiving old data to a file system, you have an option to store the data on a separate database, so that BW queries on old data can still be used for reporting.

This is very useful when using BW on HANA.

SAP BW powered by HANA, uses a multitemparature concept when deciding which data must be stored in memory and which data to push out of memory.

The data on which reporting is done on a daily basis is HOT data.

The data on which reporting is not daily or when you don't do any reporting at all (ex PSA tables and write optimised dso tables containing corporate memory) is WARM data. Warm data is offloaded from memory, when there is memory problem, to disk. This still ties the data to the database and is included with database backups and restore. SAP HANA uses a separate engine to carry out the dynamic tiering concept to offload such data.

Near Line Storage in SAP BW


The data that does not change (historical data) can be shifted to a near line storage. For BWoH, SAP IQ is the NLS of choice. SAP IQ can operate on columnar store paradigm as is the case with HANA. The hardware requirements of SAP IQ are cheaper, therefore it is a good choice to archive data out of HANA. And most importantly SAP BW has a near line storage interface to help run queries seamlessly on SAP IQ.



Email Subscription

Get every new post into your inbox by subscribing us.

Want a reason to subscribe?
1. This sitemap might convince you to subscribe.
2. We do not misuse email IDs. We respect privacy.

© 2015 sapnwnewbie. All rights reserved.