The optimize schema wizard is designed to remove some of the RDBMS joins
which are needed for cube/partition processing. It does not optimize the
mechanism for building the metadata for the cubes/partitions themselves. It
is all about the SQL statement issued when processing the cube/partition.
Can you explain more about what you mean by "takes product dimension table
and there is only default partition on cube and not having any data
slicing"? That sounds like the default operation for any cube.
--
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.
"Pravin" <Pravin (AT) discussions (DOT) microsoft.com> wrote
Quote:
I used optimize schema option of MSAS to optimize schema for product
dimension, it shows me that "schema is optimized for product dimension"
but
when i process cube it takes product dimension table and there is only
default partition on cube and not having any data slicing. Can anyone help
me
on this
Thanks
Pravin |