Hi,
We've been making some use of Master Data Services to store low-cardinality, low-churn lists which are used as dimensions in our Powerpivot model. We've never "committed" a version, we have a single version that we add and edit members in as appropriate.
I'm interested in how others go about managing versions of dimensions that change every day. For instance, we have a dimension, let's call it "Product", that has about 30K members, of which a handful might change (additions, deletions and updates to attributes) each day.
This dimension is not currently managed in MDS.
I'd like to move it into MDS to take advantage of the business rules feature, mainly to generate reporting hierarchies, of which we have several, and some of the business rules are fairly complex.
Given that I can't unlock a "Committed" version, should I be creating a new version every night, uploading the members, running the validation and "committing"? Storing a copy of the Product dimension for every day isn't such a big deal for 30K members, but I could see this becoming a problem for larger dimensions.
Thanks in advance,
Gavin