setFilter hitting the DB

[Former Member]

Hi Gurus,

I was under the impression that when we render the data once from Database (DB), using "setFilter" selects the data from the posted value and does not hit the DB again.  But when I run a trace on HANA and execute my code, I see that it does hit the DB to fetch the same values again. 

In Datasource Initial View, i have set all the values to fetch data from result set and not hit the DB again.  Has anyone checked into this issue yet or we are just believing what SAP documentation says?

Love to get your comments on this!!

Raj

[Former Member · Accepted solution]

there is no local cache mechanism in design Studio, so for sure setfilter will hit the DB.

Beat regards,

Victor

[MustafaBensan · Accepted solution]

Hi Victor,

Does the behaviour depend on the data source?  I have noticed that with BEx Queries, the first time setFilter() is applied to a particular dimension member, the response time is noticeable as it is going back to the database but if the same filter is subsequently applied the response time is almost instantaneous.  I had assumed this was due to the Local/Global Caches as described in the BW Wiki entry for OLAP Cache.  In particular, the statement "At runtime, all drilldown states of the query are cached locally to start with and then stored globally if required." seems to be consistent with the filter response times I have experienced with BEx data sources in Design Studio. 

Any thoughts on this?

Thanks,

Mustafa.

[Former Member · Accepted solution]

Hi Mustafa,

That might be because of the OLAP cache on the BW side, for design studio this is transparent, it will send the query to BW anyway (no cache here), then BW will decide from where it will send the results back (BW OLAP cache might be involved here).

Best regards,

Victor

[MustafaBensan · Accepted solution]

Thanks for the clarification, Victor.  That makes sense.

Regards,

Mustafa.

[Former Member · Accepted solution]

Thanks Gabriel for clarifying my doubts!!!