|
12 months ago ::
Jul 11, 2012 - 12:06PM
#11
|
|
|
Hi Joerg -- I hear a lot from our readers about their decision-making when choosing how to roll out HANA. What are big considerations as team decide whether to run HANA side-by-side with NetWeaver BW or running BW on HANA? Thank you...Scott
|
|
|
|
12 months ago ::
Jul 11, 2012 - 12:06PM
#12
|
|
|
Can you tell what, if any, manual tasks are necessary to prepare for migration to HANA?
|
|
|
|
12 months ago ::
Jul 11, 2012 - 12:16PM
#13
|
|
|
With the implementation of BW on HANA, how does the traditional DBA role change? Are there any unique skillsets that are now required to support/troubleshoot with the in-memory database?
The role of DBA will shift when using HANA. you have to think of HANA as a DB. When migrating to HANA it's like migrating from ORACLE to Microsoft SQL server or vice versa. After Migration you will see all tables in SAP-BW DDIC in the same way then before migration. The difference is that you do not have a DB anymore ( a physical piece of DB). Your DDIC tables live in RAM cells and all historical DB patches and additional tasks like checking indices or running BRCONNECT (in terms of ORACLE) jobs are gone. So alot of work will become obsolete with the HANA approach. On the other hand there will be new tasks like generating concepts of HANA backup (i.e. into sybase) to keep data not only in memory or flash but to keep anoffline copy of your system. New tasks like using the HANA monitoring if sufficient memory is usable and all processes have sufficient CPU etc. will arise. So easy words: your work ( I assume you still have DB driven systems) will get new areas to learn and educate yourself and some of the old work will become obsolete. Hope this anwers your question
|
|
|
|
12 months ago ::
Jul 11, 2012 - 12:25PM
#14
|
|
|
Hi Joerg -- I hear a lot from our readers about their decision-making when choosing how to roll out HANA. What are big considerations as team decide whether to run HANA side-by-side with NetWeaver BW or running BW on HANA?
Thank you...Scott
Hi Scott, this is a neck breaking question :) but let me try to answer it. WIth HANA side by side you will have no performance gain on BW reporting side. With the latest BW 7.3 and SP's you will be able to access HANA models with virtual cubes.That means you could be able to retrieve data from HANA and report in BW reporting with HANA speed. That is a reat idea to report real time data when your ERP/ECC/HCM... lies in HANA The side effect could be when combining those virtual Infoprovider with regular BW driven Infoprovider, the performance is given by the weakest member, so old BW wins and performance will be like before but at least you have real time data without any load and storage When using BW powered by HANA, all Infoprovider and BW objects will become fast. YOu may even think about the fact (matter of size of HANA system) to replicate some additional tables of ECC ... into this HANA ( should become possible) and integrate this approach by help of virtualprovider. Currently you can see the BW objects in HANA Studio but not the HANA objects in BW DDIC. This should change with latest SP. So I'd prefer the bw POWERED BY HANA approach because I thing the advantages beat the side by side. The pitfall is you have to store and load data into BW ( this will become faster due to DSO changes with HANA as well)
|
|
|
|
12 months ago ::
Jul 11, 2012 - 12:29PM
#15
|
|
|
Thanks again to all those who posted thier questions! Joerg is responding to these last posts now, before we wrap up.
|
|
|
|
12 months ago ::
Jul 11, 2012 - 12:32PM
#16
|
|
|
Can you tell what, if any, manual tasks are necessary to prepare for migration to HANA?
Yes, this is often asked Most people think of BW powered by HANA in terms of " After Migration everything is optimized automatically" No, its not. The BW is just using a very fast technology ( I will not use the word DB in this case). But, all Infoprovider will remain in DDIC as they were before. You need to run some additional steps. One of those steps is to convert Infocubes to become "Inmemory" optimized. This can be done manually by help of context menu or via SAP report RSDRI_CONVERT_CUBE_TO_INMEMORY After the run of this report all cubes or defined cubes will be flattened and the dimensions (Snow-Flake) will be gone (except request) as well as all kind of (HANA) obsolete partitioning For DSO this can be done by report RSMIGRHANADB After run the loads of DSO will become very fast and activation problems of the past will be gone with the wind. So a few tasks are related to the customer side to choose when to optimize their specific Infoproviders.
|
|
|
|
12 months ago ::
Jul 11, 2012 - 12:35PM
#17
|
|
|
Thanks to all who posted questions and followed the discussion! And a special thank you again to Joerg Boeke of BIAnalyst for joining us today! We’ll be posting an edited transcript of all the questions here in Insider Learning Network’s BI/BW Group. If you have registered for this Q&A, look for an email alerting you when the transcript is posted. Mark your calendars for additional BW and HANA events: - Join us for Joerg’s next Q&A on September 13, taking your questions on moving to BW 7.3. Follow us @ILN4SAP or join the BI/BW Group for more details and registration. - Come to the HANA Seminar in Chicago and 4 more cities in the US and Europe. Check out the details here - the first seminar is July 25! - There’s an entire track on SAP HANA & Advanced Analytics at BI 2012 in Singapore this October. I personally invite you to join me there! - Don’t forget to register for a Q&A on implementing HANA here on Insider Learning Network on July 25, with Penny Silvia & Bjarne Berg. And finally, check out this quick list of HANA resources on Insider Learning Network. Thanks again for joining us today!
|
|
|
