Hello,
I am concerned that I am doing something wrong in terms of hindering performance for my applications.
I used the information from this blog ( http://scn.sap.com/community/businessobjects-design-studio/blog/2013/12/08/design-studio-tips-and-tricks-measuring-performance#comment-473336 ) to use the information from the log to discover how HANA is interacting with design studio.
I experimented with only one data source to make my example simple.
I see that setting up any filter in the initial view does not come in as one query.
There is a query for each column you need to filter on.
The query comes in this form:
!MESSAGE [BICS HANA} (1382ms) SQL:SELECT DISTINCT "COLUMN_NAME" FROM "DATASOURCE" WHERE "COLUMN_NAME" = 'FILTER' ORDER BY "COLUMN_NAME" ASC LIMIT1
There would be multiple queries like this depending on the amount of filters you need to set up in the initial view.
This looks like it is adding a lot of unnecessary time into retrieving potentially a filter to use.
I am unclear as to why these queries are there.
The final select statement in the log shows all the previous filters in one query with the inclusion of the measures.
On the other hand, It is understandable that in the scenario where I remove the filters from the initial view and apply them on start up script, the queries are separate entities. and each has a call to HANA.
Is there a best practice for this?
Where should the filters be included to increase performance?
Using Design Studio 1.5 SP 2 with HANA.
Thanks,
Alex