I am trying to make a real time cube. I have made a dimension and a
cube.during storage design i choose ROLAP and "Allow real time updates" and
after that it made 2 aggregations. Now when i process it, i get an error that
its unable to create an index for aggregation Report_Report1* and wizard
ended with Transaction rollback.
I cannot understand why this is happening so... Does anyone have any idea
about this???

A ROLAP partition has ROLAP aggregations -- i.e. tables/indexed-views in the relational database that summarize the data at aggregate levels. When you make it a real-time partition, only indexed-views are allowed because otherwise the aggregation and the partition can go out of sync.

The error you are getting is occurring probably because of various requirements that must be met before an indexed view can be created. Take a look at the topic on indexed-view creation in Books Online and that should get you started on the changes you must make to the relational server.

If your real-time partition isn't very large, you could try with 0 aggregations and see if performance is acceptable...

Thanks,
Akshai
--
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.


-----Original Message-----
From: Sunny (AT) discussions (DOT) microsoft.com
Posted At: Wednesday, November 09, 2005 2:44 AM
Posted To: microsoft.public.sqlserver.olap
Conversation: ROLAP Problem
Subject: ROLAP Problem



I am trying to make a real time cube. I have made a dimension and a cube.during storage design i choose ROLAP and "Allow real time updates" and after that it made 2 aggregations. Now when i process it, i get an error that its unable to create an index for aggregation Report_Report1* and wizard ended with Transaction rollback.
I cannot understand why this is happening so... Does anyone have any idea about this???

If your partitions are large and you can put up with a little bit of
latency then you should have a look at the proactive caching features in
AS2k5. You can have a "near" real time olap cube.

If you have a large ROLAP partition that takes a couple of minutes to
return queries, you are better off having a near real time MOLAP cube
that returns queries in seconds, but has data that is a few minutes out
of date. It depends on a few factors, but it is impressive if you can
get it working.

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

In article <OLdqAxW5FHA.1536 (AT) TK2MSFTNGP12 (DOT) phx.gbl>,
akshaim (AT) online (DOT) microsoft.com says...

Thanks alot people!!

"Darren Gosbell" wrote: