cancel
Showing results for 
Search instead for 
Did you mean: 

Where is HANA Headed?

Former Member
0 Kudos

Hi all,

1.What type of Customers are the Target Marget for a HANA implementation?

2. How large is a HANA implementation? For ex: How many HANA consultants needed for an average HANA implementation.

3. What are the roles of a HANA consultant? How many types of HANA consultants are needed in an implementation?

4. I want to understand HANA's role beyond BW connectivity. Is it able to connect to any sourcesystem?

5. It claims to have the ability to provide realtime data, how does it provide a CEO analyze realtime data from a depertment store (Out of thousands) in NY without causing any bottlenecks?

Appreciate everyones time.

Cheers~

Accepted Solutions (0)

Answers (1)

Answers (1)

tomas-krojzl
Active Contributor
0 Kudos

Hello,

these are very good questions and I think there might be big discussion about every question (everyone is having it's own opinion) - maybe it would be good to post every question in separate thread.

Let me do my best to answer them (just disclaimer - this is just my opinion):

1.What type of Customers are the Target Marget for a HANA implementation?

Well - I would say that customers that are not happy with speed of their analytics and that have money to afford something faster. It is all about business case.

HANA is not bringing new features but rather speed (raw speed and real-time experience). If customer does not care if his BI reports will be on Monday or Tuesday then added value is low. On the other hand if you have customer that is making money on "knowing" sooner then their competition then HANA can make difference that will pay itself very fast.

Second part of this equation are costs. HANA itself as well as required HW is not something cheap.

2. How large is a HANA implementation? For ex: How many HANA consultants needed for an average HANA implementation.

3. What are the roles of a HANA consultant? How many types of HANA consultants are needed in an implementation?

That depends on the scope of project - you definitely need (in case of standalone HANA):

- hardware guy - who will connect the box to your data center (cabling, etc.)

- infrastructure guy - who will setup the network, disk setup (RAIDs), domains, etc..

- basis admin - who will be maintaining your HANA database (installations, updates, etc.)

- data architect - who will decide what schemas and packages will be needed

- security specialist - who will setup the security (and users)

- data provisioning specialist - who will replicate the data into HANA

- data modellers - who will do the modelling (attribute, analytic and calculation views)

- coders / SQL specialists - who will do the programming (procedures) and help with SQLs statements

and all consultants for all connected technologies (for example BOBJ specialist, Dashboard designers, Java developers, etc.)

Of course these are the roles - it is very likely that consultant will be able to play several roles...

4. I want to understand HANA's role beyond BW connectivity. Is it able to connect to any sourcesystem?

I would say that HANA is not connecting anywhere (at least not from data replication perspective) - you are pushing data to HANA (either using SLT or BO Data Services or Sybase replication or loading from cvs files).

There are some very nice blogs about HANA role:

5. It claims to have the ability to provide realtime data, how does it provide a CEO analyze realtime data from a depertment store (Out of thousands) in NY without causing any bottlenecks?

This is very nicely explained in SAP Master Guide (page 15 - SAP HANA Replication Technologies):

https://service.sap.com/~sapidb/011000358700000604552011

To make it short - there are three technologies:

1.) Trigger-Based Replication (SLT) - this is using database triggers to identify new/modified/deleted rows that are then transported into the HANA by SLT system - tables are same in HANA as in source system (no ETL transformation)

2.) ETL-Based Replication (BO Data Services) - you are loading data from source system using jobs and after optional ETL transformation you are saving them in HANA database - not really real-time as job is executed in certain intervals

3.) Log-Based Replication (Sybase Replication) - you are using Sybase technology to monitor database changes by analyzing records in database log and then these records are inserted in HANA database

Tomas

Former Member
0 Kudos

Hi Tomas,

Thank you for such a detailed answer. I do have a few questions:

ETL-Based Replication (BO Data Services) - you are loading data from source system using jobs and after optional ETL transformation you are saving them in HANA database - not really real-time as job is executed in certain intervals

When you say not really real time, isnt that defeating the purpose? Also BW>BODS>HANA , can this be realtime,how?

Log-Based Replication (Sybase Replication) - you are using Sybase technology to monitor database changes by analyzing records in database log and then these records are inserted in HANA database

In what events do we use the Sybase Replication?

tomas-krojzl
Active Contributor
0 Kudos

Hello

When you say not really real time, isnt that defeating the purpose? Also BW>BODS>HANA , can this be realtime,how?

"Not really real time" means that you can schedule job to run (for example) every 5 minutes - that is still acceptable delay (comparing to several hours possible with classical BI). But other two technologies are really real time (delay can be less then 1 second).

Advantage of BO Data Services ist ability to perform ETL transformation before loading data to HANA and ability to use extractors to read data from source SAP system. This is not possible with other two technologies.

In what events do we use the Sybase Replication?

In case you were part of Ramp-up and you already have it. It should not be used for new installations. SAP developed SLT as replacement for Sybase Replication.

Tomas

Vitaliy-R
Developer Advocate
Developer Advocate
0 Kudos

To add just one comment to Sybase Replication Server: indeed it is not a preferred replication method for the moment due to some limitations comparing to SLT Replication. But as SAP start migration of customers' ERP systems to Sybase ASE database we can expect comeback of Sybase Replication method. Regards. -Vitaliy