Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What should we include in a SSAS cube design documentation?

This is the initial phase of the document. I have included:

  • data models,
  • facts,
  • dimensions,
  • surrogate keys,
  • hierarchies and levels within hierarchies,
  • reports that we can pull from the cube,
  • proactive caching.

What else can we include?

share|improve this question
Why confused, sounds like you've made a good start. I would add a users perspective by defining access roles and privileges. Maybe add administrative and maintenance schedules. – Carlo Kuip Dec 19 '11 at 20:01
@CarloKuip I think your suggestions with some explanation on each one would make for a good answer to the question. – Yannis Dec 20 '11 at 10:16
Does this belong here (i.e. programmers), or on DBA perhaps? – sdg Dec 20 '11 at 20:41

How About the a source of the data and descriptions of all the ETL\ business rules needed to load the Cube?

It's a common misconception that to build data Cube all you need to do is learn how to model the Star Schema. But the Truth is getting all data from multiple sources, cleansed and married together in a unified format is much harder then building the cube. It mat be a good idea to document some of that stuff.

Also throw in Data Dictionary, those are always nice to have with a complex BI system.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.