Skip to Content
Author's profile photo Former Member

Who’s Talking About SAP HANA? Find out on this “Conversation Heat Map”

With SAPPHIRENOW + ASUG almost upon us, I wanted to introduce a new tool we’ve developed to help you “visualize” social media conversations. We’ve dubbed this a “Conversation Heat Map” and the concept is quite simple: By mashing up Twitter + Google Maps, you can view tweets in real-time from people around the world. In this first iteration, we’ve decided to focus on tweets related to SAP HANA because it’s such a hot topic with lots of interesting conversation.

Check out this link to see it in action. Would love to get your thoughts and feedback!


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      I'm getting more impressed by the way SAP markets HANA.



      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Thanks, glad you like it!

      Author's profile photo Muralikrishnan E
      Muralikrishnan E

      Nice and Impressive App!



      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Thanks very much!

      Author's profile photo Former Member
      Former Member

      Taking us to the future

      Author's profile photo Former Member
      Former Member


      Thank u For sharing this unique article. Definitely a life saver.

      this is the situation:
      - <a href="">SAP S/4 Hana</a> 1.0 SPS12
      - There is no PRELOAD flag set for any table
      - 3TB of column tables are loaded during normal workload
      - The RELOAD feature is active.
      During a HANA revision update (after the executables were updated) the delivery units are going to be imported. If the parameter "reload_tables = true" was set before the update process gets started, the system will reload all tables (3TB) which were loaded during normal operation and recognised by the reload-mechanism.
      Due to the high I/O load, the delivery unit import will be extremly slow and will just complete after the table reload has finished.
      My idea was to set the reload_tables parameter to "false" before the update begins, then do the update and set the parameter back to "true" afterwards in combination with a HANA restart.
      Does the HANA system lose the information which tables were loaded, when I set the parameter to "false" or are they saved somewhere and will be noticed when I re-activate the parameter?
      My fear is, that the information is lost and when I reactivate the parameter the system will rescan all loaded tables at this moment (which are just a few) and so all the other tables needed by the SAP system for normal work don't get loaded at startup time.
      If the information gets lost: Is there a way to manually save the information which tables are loaded at the moment and to restore this information to the system after the parameter gets activated again?
      Excellent tutorials - very easy to understand with all the details. I hope you will continue to provide more such tutorials.