Evaluating cube SQL that creates Measure

I am using Visual Studio 2008 Analysis Services and processing the AdventureWorks database to create and process a cube.  One of my measures is the Sales Amount field from the FactInternetSales table.  When I click and drag that field onto an otherwise blank crosstab, my value is less than 29358677.2206503, which I know it should be.  The study video I'm following shows that value, as do I when independently verifying the value by writing a view against the table.  

I suspect that when the measure is defined, something in the SQL statement puts a filter on the field, resulting in a value that is too small.  I do not know how to test this hypothesis.  Please help.

Thank you, ~Peter Ferber
Who is Participating?
PeterFrbConnect With a Mentor Author Commented:
I did not succeed in using Profiler to unravel this, but I did finally get this piece to work.  The problem, it turns out, was in the Attribute Relationships.  I've been viewing the most excellent video series on Analysis Services (http://www.learnmicrosoftbi.com/Videos/tabid/75/Default.aspx), for which one must register to see all the material, but it's free to join, and I skipped ahead to section 109, which demonstrates Attribute Relationships.  Once I had this correctly, the numbers were suddenly correct!
Actually, you may find that one of your dimensions has a default value.

Use Profiler to see the query that's being, and then start pulling that apart.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.