cancel
Showing results for 
Search instead for 
Did you mean: 

Is there any workaround to overcome HANA's limitations?

Saif
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi All,

Is there any workaround to overcome HANA's limitations like:

1. Depth of SQL parse tree-  255

2. Number of joined tables in an SQL statement or view- 255

About limitation 1., Is this limitation at statement level or this is for a view entirely? (I get that error mostly when I am trying to activate a scripted calculation view)

About limitation 2. One way is to break the SQL statement into multiple, whenever the JOIN exceeds 255.

However, even if we are able to achieve this, my use case, we will hit the next limitation in the view which is, :Number of columns in a view- 1000

Is there a better approach to overcome these?

Any help/suggestion is highly appreciated.

Regards

Saif

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member182114
Active Contributor
0 Kudos

Hi Saif,

How are you reaching such limits?

It's your one code, 1 SQL with coded yourself?

It's an SQL Script that on instantiation it's becoming a big one?

What is the use case of such big construction?

Regards, Fernando Da Rós

Saif
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Fernando,

As part of one of our HANA models, we are using joins to transpose rows to columns. Due to the number of joins, we hit the 255 limit for the parse tree depth which results in an error.

Its a one SQL statement I would say, in a scripted calculation view.



Regards

Saif

Saif
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Fernando,

As part of one of our HANA models, we are using joins to transpose rows to columns. Due to the number of joins, we hit the 255 limit for the parse tree depth which results in an error.

I would say its a 1 SQL statement in a Scripted calculation view.


Regards

Saif

lbreddemann
Active Contributor
0 Kudos

These are fixed limitations and you'll have to change your models in order to make them work.

Transposing rows to columns had been extensively discussed here on SCN and doing this via joins is likely not the best approach anyhow.

former_member182114
Active Contributor
0 Kudos

Hi Saif,

I agree with what Lars metioned, your case is not a case for extend de limits but rethink your plans.

Even if it should possible with such big constructions you will for sure reach in another question soon.... "How make my HANA bigger to process my hungry SQL".

Do a search on SCN for topic pivot columns and you will face not only the difficult but also ideas.

Anyhow, end up with 1000 columns of output appears to me also with another question for redesign.

Regards, Fernando Da Rós