Hello,

I wonder if someone give a clue what is happening on my project. I use SQL
2005 Standard Edition with SP1, the DB and SSAS are on the same machine. The
messages and names given are translated back to English, I hope you can find
what I describe on your system.

I have a cube that needs quite a while to load when data was added, so I
tried to change it from MOLAP to ROLAP, just to see what that performs like
and how it works. The cube can be rebuild in MOLAP without errors.
So I open the cube in VS2005, go to "Partitions" and click "Design
Aggregates". While using MOLAP, the slider is all the way to right. Since my
Standard-Edition does not allow the usage of "ProActive Caching", I have to
go into options, disable that setting, and choose ROLAP from the pulldown.
The rest of this entry form is completly disabled now, so nothing should be
wrong there.
The Slider on the main dialog is now disabled and on "automatic MOLAP",
while clicking "Options" again shows I am still using ROLAP. Strange, but
maybe that is the way it is.

I save all my settings and choose to "Create" and "Deploy" this one to the
server. It begins with the processing of the dimensions (*1) and continues
to the cubes.
The cube processing is stopped at some point, and I get a warning and an
error. The warning reads something like "Aggregations for the level (all,
all, all...) is not allowed in ROLAP and will be skipped", I think I
understand that as "To get this value the whole DB would have to be counted,
and I am not doing that" - fair enough.

The error afterwards breaks the process, it reads:
"OLE DB or ODBC error. The Index-Object <tablename>_8_10_14_12_12_12-View
cannot be created, because the derived table <tablename> (defined by a
SELECT Statement within a FROM Statement) is referenced. Remove the
reference to the derived table, or do not index the the view.; 42000"

Well... yes... what does that mean?
The error mentiones a derived table created by a SELECT in a FROM - I have
non of this in my DB. It mentions an indexed view - I do not use any views
for the olap setup, only tables.
It sounds as if the SSAS was trying to either create a view, or add an index
to a view. Does it do that if you choose to run on ROLAP? To make sure it
could do that if needed, I had the connection use the Administrator account
and changed the SSAS process to run as Admin instead of LocalSystem (this is
mentioned on the same warning box that tells me my Standard Version cannot
use ProActive Caching). This did not cure the error, though.

So - any idea what this could be?
Ralf

(*1) For my understanding of ROLAP: I can access the latest data without
having to rebuild - right? But the dimensions WERE processed, so the first
sentence is only true as long as the dimensions have not been added to. If
they got new elements, a processing is needed to allow access to them -
right?

Sometimes AS needs to use a generated query for the partition (e.g. if there
is a Row binding measure, or multiple data sources, etc.). If you process
the partition as MOLAP, you can see the query being generated and see what
the derived table looks like -- this may give you a hint about why the index
can't be created and you could create the index manually...

Thanks,
Akshai

--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.


"Ralf Mayer" <Ralf.Mayer1 (AT) gmx (DOT) de> wrote