Skip to Content
avatar image
-1
Former Member

solution manager sizing on HANA

Hi,

I used the quicksizer to do a SM sizing for HANA, for technical monitoring and EWA's for 25 systems. The numbers I get are crazy. It says that I need about 200 Gb of RAM for HANA? I think this is not realistic. What is the minimum RAM and CPU I need to have SM 7.2 on HANA? Please advise. Thanks

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Dec 08, 2016 at 07:18 PM

    Why would 200 GB of RAM be outrageous? HANA boxes don't come much smaller than that. Solution Manager has a lot of features which could add to the need for more ram even in a basic scenario. For more info take a look here as well.

    https://websmp204.sap-ag.de/~sapidb/011000358700000519272005E#SAP_Solution_Manager

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 12, 2016 at 12:28 AM

    Hi Steven, Thanks for the reply.

    Our current solution manager is running on less than 80 Gb Oracle database. If I consider a one on one comparison of my existing DB size, and take HANA's compression in to account, going for a 250+ Gb Box (TDI) is not an easy sell. It is outrageous. We are running our production instance of Business Suite on HANA on an appliance which is less than 250 Gb. As I mentioned, I am trying to understand the minimum requirements. I cannot agree with the quick sizer for running a bare solution manager with close to 200 Gb RAM. I would probably have to look in to some formulas which can help me get the right size. Please let me know if you can enlighten me in this scenario. Thank you!

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Jim

      SAP Solution Manager 7.2 isn't optimized to run on SAP HANA. That's where the size comes into play because there is nothing much specific done in terms of simplifying data structure for example. It has to be able to run on AnyDB still also so it's like running Suite on HANA (without too much optimizations for SAP HANA). At best you get some compression gain in terms of data (if your current DB isn't compressed already). You also need 1/2 RAM (give or take) to have as spare RAM to perform calculations so that's why you might actually need more RAM compared to before. XS size comes back with 200GB as a recommendation in SAP HANA quicksizer.

      You should be able to use Suite on HANA sizing report in SAP Solution Manager to get an idea on the size of your SAP Solution Manager installation if you would migrate it to SAP HANA. Of course SAP Solution Manager 7.2 does have a few new components still as well like embedded Power Designer which also take up space in the database.

      You can deploy a SolMan 7.2 SP3 via SAP CAL into Amazon AWS. That takes about an hour to set up and then you can check the size of the SAP HANA database platform on a nearly empty SAP Solution manager 7.2. An empty SolMan 7.2 takes about 90 GB on a non SAP HANA database. If you enable technical monitoring and EWA's for 25 systems I can imagine you will make the system grow and you can easily end up with that 200GB recommendation I suppose since you still have two separate stacks that both consume DB data + additional data coming from technical monitoring. A classic SolMan would give 373GB DB space if you would state you enable 25 systems for EWA + Technical Monitoring. Going for SAP HANA should divide this by a factor of 2 (or 3 maybe) most likely (since it's not optimized). Let's assume 3 then you go to around 100GB DB space and you need calculation space in RAM still so to me it sounds like 200GB is reasonable from a sizing perspective.

      I've got much larger installations of SolMan and much more consumption of SolMan at customer side which makes going for SAP HANA even more difficult.

      Best regards

      Tom

  • avatar image
    Former Member
    Dec 12, 2016 at 03:25 PM

    Tom, much Appreciated. Thanks!

    If you don't mind me asking a follow on question - Would you be able to tell me what I miss if I go on a non-HANA DB on SM 7.2? I hear a lot of Fiori tiles, analytics and dashboards, and I am afraid if all of that would work on a Non-HANA system.Thanks!

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Jim

      Nothing much so far, all those things work fine on non SAP HANA DB as well. SAP Solution Manager 7.2 has to support anyDB because it's not a new product so there are no product differences from that perspective. The only way something can be introduced that is different is through add-ons (third party for example) as far as I know in this version of the product. Otherwise, all scenario's will work on both SAP HANA and on AnyDB.

      There might be specific add-ons (like I mentioned) in the future which are considered separate products (read, you will need to pay something) that can really leverage SAP HANA. Third party vendors can come with those kind of solutions.

      SAP HANA has the SAP HANA search engine so you don't need a TREX. If you go AnyDB, you need a TREX, preferably (to avoid issues), a dedicated TREX per SAP Solution manager system to cover the search functionality and to have business process modeling available in solution documentation (without search, you cannot do business process modeling with the embedded power designer as the first thing it does is look for an index to search through available models).

      For the rest, as already mentioned, you get the same thing in the end, perhaps a bit slower but then again, SAP Solution Manager 7.2 is not optimized (or simplified for that matter) to run on SAP HANA so the gain is not like on the ERP side with S/4 HANA.

      My expectation is that there will be plenty of customers still running SAP Solution Manager 7.2 on AnyDB. SAP HANA is of interest from a strategic point of view in my opinion to place it under SAP Solution Manager 7.2. As a strategy to go SAP HANA only or to introduce SAP HANA into the organization if there isn't really experience with it.

      Best regards

      Tom

  • avatar image
    Former Member
    Dec 12, 2016 at 06:43 PM

    Many thanks, Tom!

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 25, 2017 at 12:16 PM

    Hi
    200 GB sounds quite big no. for SolMan, with the limited archiving capability of SolMan the DB will keep increasing like crazy in case of large environments.

    What practical options are available to keep DB below 100 GB?

    Thanks

    Add comment
    10|10000 characters needed characters exceeded