Hi
Just spent the last two days trying to get past the "Failed to create index" error message when setting up a ROLAP cube. The info from Yuan Shao was helpful relating to SQL Server and SQL database options (QUOTED_IDENTIFIER, ANSI_NULLS, etc.)

However, I've noticed that other configuration issues can also apply that I haven't seen mentioned anywhere. For example, if the underlying fact table has a different owner (lets say XYZ, for example), the Analysis Manager could create the view with dbo as the owner, and then when it tries to create the index, it fails because the view can't have a different owner than the table its tied to. There are ways you can control this, either by tweaking the data source connection options, or by setting the aggregation prefix down in the advanced options for the partition, but this can be tricky and non-intuitive

The real problem with all of this is the error message is just so terse and non-informative. It won't tell you what CREATE INDEX statement it was trying to execute, and it won't give you any information about why it failed. You are just flying blind trying to troubleshoot this error message. This absolutely needs to be fixed in my opinion

- Kevin