Recalculation of Data
Posted: Thu Jul 28, 2011 1:30 pm
Hi forum,
we use our cubes for BI reporting, typically loaded with data overnight and queried through the day, with no new data going in.
What I am finding (looking at process monitor) is that if I run a query (Via BI report) there is a lot of processor usage. This I can understand the first time I run a report. But if I run the same report again (no parameter changes), I'd expect my cube to get it's results from RAM and barely touch the CPU.
Might I have set up something by accident that is forcing recalculation? I've got skipcheck and feeders in there, not that I suspect that would cause a problem
Cheers
ps - I doubt it makes any difference, but I recently reorderd dimensions, putting my measures dimension first, which cut the cube to about a quarter of it's size and drastically improved performance. Fairly sure this is unrelated, but possibly points to corruption or something nasty!
we use our cubes for BI reporting, typically loaded with data overnight and queried through the day, with no new data going in.
What I am finding (looking at process monitor) is that if I run a query (Via BI report) there is a lot of processor usage. This I can understand the first time I run a report. But if I run the same report again (no parameter changes), I'd expect my cube to get it's results from RAM and barely touch the CPU.
Might I have set up something by accident that is forcing recalculation? I've got skipcheck and feeders in there, not that I suspect that would cause a problem
Cheers
ps - I doubt it makes any difference, but I recently reorderd dimensions, putting my measures dimension first, which cut the cube to about a quarter of it's size and drastically improved performance. Fairly sure this is unrelated, but possibly points to corruption or something nasty!