Should proactive caching be used instead of processing dimensions?

Question

I am confused about best practice for updating cube data throughout the day. We have a small order processing environment, where I would like to update a dashboard containing Order statuses. I am able to get this to work by creating an SSIS package and scheduling it to run every 4 minutes. This works.

But when I disable the SSIS job above, and instead turn on Real-time ROLAP on all the dimensions and the Cube, nothing ever changes in dashboard. Do I misunderstand the purpose of proactive caching?

I'm using SQL Server standard containing our production data, but our Analysis Server is Enterprise, in case that makes a difference. I'd also be willing to use Automatic or Scheduled MOLAP if that works.

Answer 1

no, you did not. I think you have configuration issues.

I assume the job you disabled was coping data from your database to your data warehouse, right? And your cube reads from your data warehouse, right?

so now, your OLAP database is being updated (by your application) but the changes are not being pushed to the cube (because the job is off)

Proactive caching (specially with ROLAP) is a way to get your data live without having to schedule a cube refresh for every x minutes. But the job that populates your DW must still be running.

I can guess that the package you disabled was, besides updating the DW, also refreshing the cube. Check it's source.