Hi one of my requirement:
For each Patient I have to pull lots of information using multiple lists/crosstabs. if I use one data container for each patient I will get all the information in one which is very big row with multiple lines which users does not want to see all in one row they want the information breaking down into the separate boxes.
so I need to break down information into separate lists or crosstabs
one is for Patient information(number of data items)
one is for patient vitals(number of data items)
one is for In and Output(more than 10 data items)
one is for weights etc..(more than 8 data items)
one is for some other information
so I am using master detail concept. first I just take one list with patient number in that column I am using a table with multiple rows and columns to put other list/crosstab and giving master detail relation to each data container with master query.
but muster detail is killing the performance since I need to run all the patients in one page
queries performance is absolutely fine
Any help I can get from here friends, your help is big thing for me to achieve this
Without seeing the data structure in detail, this may be one of the cases where setting up master detail into a parameter in the detail query (rather than into a data item) would improve performance. Of course, that presupposes that you actually use a different master query.
You can have multiple layout containers on a page that are all fed by the same or different queries which may share the same parameters as filters. You can also associate a query to a page and layout the items free form using blocks and tables. I'm not really clear why you need master-detail. Is it one page per patient like a fact sheet?
There are a couple of techniques to doing this.
1. A setting change that will send one query down to the database.
2. You feed the query to two local queries -- Master and Detail. This local processing forces only one query, and in one of the rare cases, local processing can provide significant performance improvements over DB.
Have a read...
https://www.ibm.com/developerworks/data/library/cognos/reporting/performance_and_tuning/page582.html