on 06-17-2013 11:21 AM
Dear Experts,
I want to understand what are limitations/challenges experienced during HANA sidecar engagements.
Thanks.
Br,
HG
Hi Hidresh,
The advantage of sidecar is that you can continue using your existing system as-is while using HANA as a secondary database.
The way the current SAP systems work is, the data is transferred from database to application layer and calculations are performed in application layer. Here you have significant latency between disk to memory transfer and then calculations in application layer.
HANA databse on the other hand is optimized for mass parallel processing and performs calculations in the database layer and only submits a result set to the application.
Below are several limitations -
This blog gives you a general idea of how you can use HANA as a sidecar approach.
You can also view the following blogs - part_1 and part_2 to see how you can achieve this.
Thanks,
Sharan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Hirdesh,
We have successfully used HANA Sidecar and the only thing I can add to Sharan's comments is one of our challenges around code review. For example on the HANA side of things we have code reviews for any new models that are delivered however sidecar queries that are written in SAP ABAP could potentially be changed and we could lose visibility. For example say we approved a sidecar query to pull 10 fields from a table in HANA. Everything is great and they are consuming lets say a gigabyte of memory. Then a year from now somebody on the ABAP side decides they want to change their query and bump it to 20 fields. This is a simple example but you can see they could suddenly be consuming more of HANA memory than originally intended. So for this reason it's important to somehow have cross-functional code reviews so that the HANA team is always aware of what could be changing at the sidecar level.
That's my little tidbit, I hope it helps.
-Patrick
Going along with Patrick's statement of change, one other challenge you can add to the list is upgrades. If you upgrade your kernel or netweaver release of your SAP source system, you also have to ensure that all your custom abap programs remain unaffected. If you use SLT/DXC for loading to HANA, then you also need to see how these items are affected during/after an upgrade.
Another thing I would add is you basically have redundant data, 1 set in your transaction system and 1 set in the HANA database.
The final thing is if you have a disaster/multi-node/standby scenario. You need to ensure that if HANA server crashes, it doesn't become a single point of failure, or if you have to recover your system, the HANA system must remain in sync with data in your transaction system, etc.
Thanks,
Sharan
Ptarcik, We are about to start implementation of HANA Sidecar approach. I would like to know your experience and lessons learned from Sidecar approca. Is it possible to have a brief call to discuss this? I would appreciate your time. You can reach me at sarekapudi@commscope.com.
Thanks!
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Can someone please share the major steps involved using "HANA HEC as a Sidecar" approach for ERP Finance data/tables including how to install HEC side car ?.
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.