I have made a cude that has two dimensions and one measure. The problem is
when I browse the cube the measure (Actiondata) is almost ten times more then
when I use query analyzer. Could it be how I set up the cube or could it be
the data in the fact table?

It could be the way you have set up your dimensions. If you have not
optimized your schema it will be inner joining your dimensions to the
fact table and possibly producing duplicate records.

When you process the cube from analysis manager you will see the SQL
statement that AS has issued in order to get the fact data. It takes a
bit of mucking around, but it is possible to copy the statement and
paste it into query analyzer so that you can debug it. (The trick is to
click on the node above the SQL statement and then use the arrow keys to
move down onto the SQL statement itself, which you can the copy with a
Ctl-C)

I find this technique invaluable with dimension problems, you tend to
find issues with duplicate keys or names, it really depends on how your
dimensions/cubes are structured

--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell

In article <48B60C6E-8636-4F54-813E-8162F1CA81DC (AT) microsoft (DOT) com>,
AB (AT) discussions (DOT) microsoft.com says...

The other way to get the SQL statement is to turn on the system-wide
processing log file (which is an important best practice -- See the AS
Operations Guide). This allows you to record *ALL* processing work which can
be extremely important as a debugging resource.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Darren Gosbell" <dgosbell_at_yahoo_dot_com> wrote