Skip to Content
BW (SAP Business Warehouse)

Multi Temperature Data

Tags:

What does the 'Non-Active' data concept mean for BW on HANA?

With BW NetWeaver 7.3 SP8 SAP has introduced the 'non-active' data concept, which supports an optimized RAM management by proactively managing and categorizing 'warm data'.

For details please see this blog.

http://scn.sap.com/people/thomas.zurek/blog/2012/10/15/how-bw-uses-hanas-memory-in-a-smarter-way

There is also a recorded Live Expert Session (LES) available about this topic from January 9, 2013. The slides of the presentation are posted there as well.

http://service.sap.com/~sapidb/011000358700001147782010E

Where can I find more information about SAP's new native NLS solution for BW with Sybase IQ?

With BW 7.30 SP9 (March 29, 2013) and BW 7.31 SP7 (April 15, 2013) SAP released their own native NLS solution for BW with Sybase IQ. No middleware or 3rd party solution will be required anymore with this solution. It is an DBSL based solution which allows for a very tight integration. By leveraging the mass insert functionality of IQ loader excellent write performance is achieved. This fits perfectly into a information lifecycle management strategy to manage hot, warm and cold data.

http://scn.sap.com/docs/DOC-39944

Nice short demo: https://www.youtube.com/watch?v=3DlRd_-kG3A

First Guidance document for implementation and setup:

https://scn.sap.com/docs/DOC-39627

For more information check out a recorded Live Expert Session (LES) available about this topic from January 10, 2013. The slides of the presentation are posted there as well.

http://service.sap.com/~sapidb/011000358700001147782010E

There is also an Rapid Deployment Solution available for SAP's new native NLS solution for BW with Sybase IQ.

http://service.sap.com/rds-nls

Is there also a more executive summary about the new BW NLS solution with Sybase IQ?

There is a very good clip on published YouTube that gives a brief summary about IQ NLS for BW suited for executives.

https://www.youtube.com/watch?v=FdtdAhTQYSg

Is it possible to change an existing InfoProvider where data is already offloaded to NLS without having to load the data back to BW first?

There are several changes that can be applied to an existing InfoProvider without the need of loading NLS data back. Please refer to the NLS FAQ.

http://scn.sap.com/docs/DOC-54469


I heard about 'Extended Storage' and 'HANA Dynamic Tiering' in the context of BW 7.40. What is it?

HANA Extended Storage is a new HANA feature introduced with HANA SPS07 that BW 7.40 fully incorporated as warm data store. It is a very strong warm data management capability where before only the non-active concept was available which was introduced as warm data feature in BW 7.3 SP8. The feature has been in pilot phase and is planned to be released in November with HANA SPS09 as SAP HANA Dynamic Tiering. Have a look at the following linked document that explains the details about this feature, the roadmap deck of BW 7.4 SP8 and the online documentation for more details.

https://hcp.sap.com/content/dam/website/saphana/en_us/Technology%20Documents/SPS09/SAP%20HANA%20SPS%2009%20-%20Dynamic%20Tiering.pdf

https://scn.sap.com/docs/DOC-58173

http://help.sap.com/saphelp_nw74/helpdata/en/f6/99e81daef24dfa8414b4e104fd76b7/content.htm?frameset=/en/bb/df686dc0d94f779b5c11d06753da95/frameset.htm&current_toc=/en/a0/efe8240b754ee4ac1acc1ff57fa87c/plain.htm&node_id=37&show_children=false

http://scn.sap.com/community/bw-hana/blog/2014/09/29/bwonhana-extended-storage-and-dynamic-tiering

Further technical information is available in OSS note 1983178.

http://service.sap.com/sap/support/notes/1983178

Does SAP HANA Dynamic Tiering replace IQ NLS?

Not at all. HANA Dynamic Tiering covers a different data area within a BWoH system and helps to improve TCO for data that is kept within the HANA database versus moving it to an external near-line storage. Look at the BW 7.4 SP8 deck in SCN where the difference between NLS and HANA Dynamic Tiering is clearly described. More information is also mentioned below.

https://scn.sap.com/docs/DOC-58173

http://help.sap.com/saphelp_nw74/helpdata/en/f6/99e81daef24dfa8414b4e104fd76b7/content.htm?frameset=/en/bb/df686dc0d94f779b5c11d06753da95/frameset.htm&current_toc=/en/a0/efe8240b754ee4ac1acc1ff57fa87c/plain.htm&node_id=37&show_children=false

When should a customer use SAP HANA Dynamic Tiering and when NLS? What is SAP's positioning on HANA Dynamic Tiering vs. NLS for the BWoH use case?

HANA Dynamic Tiering and Near-line Storage are two very different concepts. They do not compete and rather complement each other. The idea of an NLS solution  or cold store is primarily to take historical and aged data from the reporting layer (i.e. InfoProviders that end users directly report on) that is static and thus doesn't require much of the BW functions except reporting/BEx functionality, and move it out of the system into a separate environment while fully supporting all reporting needs transparently. This means the end users and all existing reports are not affected by moving data out of the primary database into a near-line store. Due to the reduced functional requirements towards that data it can be moved to a separate environment which provides lots of benefits from a operational perspective. High availability and disaster recovery requirements can be completely separated including the frequency of backups and other SLAs. That's why an NLS solution will always store the data in an environment separate from the primary database of the system.

HANA Dynamic Tiering targets a different data area. The primary goal of a warm data store in a HANA environment is to optimize memory usage. Warm data typically requires the full set of functionality of the HANA platform and the BW application running on top even though data processing in that area is usually very basic and mostly doesn't go beyond simple write and read functions. That means that warm data doesn't necessarily need all the horse power HANA provides by storing the data in memory all the time and thus keeps the data stored in Extended Tables outside the in-memory store at all times either on disk or flash drives. This also means that warm data is not suited for complex and workload intense reporting scenarios where indeed the power of HANA's in-memory processing would be crucial.

Have a look at the following linked document that explains the details about this feature, the roadmap deck of BW 7.4 SP8 and the online documentation for more details.

https://hcp.sap.com/content/dam/website/saphana/en_us/Technology%20Documents/SPS09/SAP%20HANA%20SPS%2009%20-%20Dynamic%20Tiering.pdf

https://scn.sap.com/docs/DOC-58173

http://help.sap.com/saphelp_nw74/helpdata/en/f6/99e81daef24dfa8414b4e104fd76b7/content.htm?frameset=/en/bb/df686dc0d94f779b5c11d06753da95/frameset.htm&current_toc=/en/a0/efe8240b754ee4ac1acc1ff57fa87c/plain.htm&node_id=37&show_children=false

Further technical information is available in OSS note 1983178.

http://service.sap.com/sap/support/notes/1983178

There is also a nice blog that goes more into details about the positioning of NLS and Dynamic Tiering.

http://scn.sap.com/community/bw-hana/blog/2015/02/01/efficiently-managing-your-data-in-sap-bw-on-hana

Where can I find what NLS partner solutions are certified for BW on HANA?

Please check the Application Development Partner Directory. Just type in 'nearline' into the search field. That should list all certified partner solutions for NLS. Click on the partner names to get a list of all their active certifications.

http://global.sap.com/community/ebook/2013_09_adpd/enEN/search.html