I am trying to create a ROLAP cube with 'Enable real-time updates' enabled.
When I go to process the cube it fails stating,

Creating indexes for Aggregation '5111111111'
Failed to create index.; Time:7/1/2005 7:38:46 AM

Cannot enable real time updates on this partition without indexed views.;
Time:7/1/2005 7:38:47 AM

Can anyone help me debug this? Is there any way to get a more descriptive
error from Analysis Services?

thanks,
Tim

What is your RDBMS? We reply on indexed views for this feature. It sounds
like AS doesn't think your RDBMS supports it.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Tim Chapla" <tchapla (AT) nospam (DOT) turnleaf.com> wrote

Im running SQL Sever 2000 Developer Edition - SP3 on Windows Server 2003

"Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote

Hmm.. I don't know. Try running Profiler and see what TSQL is actually being
sent. That might give you a clue. Sorry.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Tim Chapla" <tchapla (AT) nospam (DOT) turnleaf.com> wrote

The last two statements that fire are:

select objectproperty( object_id('dbo.IRACR_IRACR_TE'), 'isindexable' )
IF @@TRANCOUNT > 0 ROLLBACK TRAN

When I fire the
select objectproperty( object_id('dbo.IRACR_IRACR_TE'), 'isindexable' )
it returns a 1 telling me that the view is indexable.

Any ideas?

thanks

"Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote

real time olap use indexed views, creating this type of views required
specific configuration during the view creation.
DCount measures can't be used in Realtime olap, only simple calculation
(sum, count) can be used.
If your source table allow NULL values for the columns used, you can't use
indexed views against these columns.
If you use views for the source of the cube, insure that your view reference
the schema where you tables are in the from clause: from dbo.MyTable and not
from MyTable

Maybe you have some options setup at the server level. (like the set
arithabort option )
Read the BOL about indexed views to learn more about the requirements

Try to create a simple query in the query analyzer like this:
select Column1, Column2, count_big(*)
from dbo.MyTable
group by Column1, Column2

then use the index tuning wizard and insure that you want to create an
indexed view, this will help you to identify if your SQL server installation
can create the indexed view.
Or you can follow the BOL to creatre the indexed view by yourself.

good luck!


"Tim Chapla" <tchapla (AT) nospam (DOT) turnleaf.com> wrote

On a Real-Time ROLAP partition, you can avoid the creation of indexed
views by designing 0 aggregations - we have a couple of small cubes that
are designed this way (Real-Time ROLAP partition only contains the
current day's data). But query performance will be a problem with larger
cubes.


- Deepak

Deepak Puri
Microsoft MVP - SQL Server

*** Sent via Developersdex http://www.developersdex.com ***