Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
After reading much of the documentation, I’m still unclear about proactive caching being set in various places: in the Partitions, on the Dimensions, and on the Measure Groups.
What is the difference between setting them in these various place, and where would one need to set proactive caching for SSRS reports to be current (in my case I’d be using scheduled polling)?
When you configure proactive caching for a dimension, then that will keep the dimension current with the source. A customer dimension is one where you might consider enabling proactive caching…where as a date dimension is (typically) static so you wouldn’t need to configure proactive caching for that one (unless you had a current date flag or something like that).
MeasureGroup and Partition proactive caching is specific to your fact data. The difference is simply the granularity. If you want all partitions in the measure group to use the same proactive caching settings, you would configure it at the measure group level. However, if only the data in the most recent partition is changing (say current month), then you could just configure proactive caching on that particular partition.