I have a question not a problem, I use data from a datawarehouse. In some fact tables we also use "dimensiondata" as fields.
For example, a have 1 million rows in my fact and on every row there is a errorcode. I now want to use errorcode as my dimension in my pivot and calculate a measure from my fact table. No the question, is it better to keep the errorcode as an own dimension in the model or does this matter when I calculate this in my object (for ex pivot table)?
Not sure if understood right. Is it something like (5 rows X 1 M cols) Vs (1 M rows X 5 cols)? If so, it would be better to convert the data in the script using probably Crosstable statement. That would not only improve the front-end performance; would simplify the expressions to get your desired result as well.
If you do the transformation at the back-end, it would increase the reload time which is one time job before it gets to be refresed, while for every selection in the front-end memory performance indicator would get a hit. Hence, it would probably be better to take transformation to the script.
Ah.. I guess performance wise(at the front-end) loading a single table(with all 1 million dimvalues) would be better. Because that would require no hopping at all. And if no hopping is required, wihout having to create possibly combinations of data, possibly less memory would be required.
Ok, with hopping you mean that when calculate in object, qlikview wont need to "look" into another table before present the result in aggregation? This is also front end, because when select the pivot is recalculated.