.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Re-processing Dimensions with a ROLAP cube

Posted By:      Posted Date: September 22, 2010    Points: 0   Category :Sql Server

Hi all.

I have set up a ROLAP Cube because of the advantage that you do not need to re-process the cube.  AS will always go to the underlying data source for the most up to date data.  Unlike MOLAP you do not need to re-process your cube to refresh the data.

BUT.  I find this is only true for my FACT data (or for my measures).  Say for instance my dimension changes - I add the member "Australia" to the country dimension.  This new data is NOT filtering down to AS automatically, I need to re-process my dimensions for the cube to be valid again.

So my question is this.  If you have dimensions changing with each datawarehouse load, what is the advantage of ROLAP?  Is there a way for ROLAP to figure out that a dimension has changed and re-process it automatically?



View Complete Post

More Related Resource Links

how ssas generate sql queries when processing dimensions and partitions?

hi all, how does ssas2008 generate sql queries to read data from the source, where processing dimensions and partitions? is there any reading meterial that clearly explains how the sql queries are constructed according to properties of dsv, dimensions and measures and partitions.   thanks in advance.Andrew Chen Interested in BI related technologies

Cube Processing Error

Hi All when i process the cube some times i get the error  "OLE DB or ODBC  Error: Operation Cancelled; HY008. Internal Error: The Operation Terminated unsuccessfully  " https://connect.microsoft.com/SQLServer/feedback/details/286505/error-in-processing-cube?wa=wsignin1.0 In above link Microsoft they said to increase Query time out, i made it 0 even it repros I am using SQL Server 2008.   Thanks

Problem in Cube processing

Hi All, I have created cube and processed with the setting "Stop Logging",and it would take 30 min to complete processing with the error shown  Error in Olap storage engine The attribute key cannot found when processing table "Factcalldata", column programid,value 7070.the attribute is Programid.   Kindly let me know is this is the reason which is responsible for Longer processing Time ,i have created partition and aggregation in all measure groups.   Regards Amit  

Cube processing

HI All, I am new to SSAS and but i suppose to work on cube part. I have created cube with two partition both of 5 days using getdate()-10 to getdate()-5  and getdate (4) to getdate() ,,,,so tel me if i process full cube once and then other partition in full process,then will the 5 day process data overite the full data into 5 day data or not.   regards Shraddha

Cube Processing

Hi all, I have a cube and it is processed every 6 hours. 3 different process calls the SSIS package through SQL Server Agent to process the cube, and they all may call the SSIS package at the same time. But for that I set an Indicator which tells the cube is processing and it waits for a minute and re-checks it and then processes the cube. My problem here is while the cube is processing other ETL jobs might update/delete/insert the data into Fact Tables. What will happen when cuube is processing and these things are done simulatneously. Can anyone explain what will be the possible outcome. Thanks Vineeshvineesh1701

daily complete cube rebuild four dimensions and fact table including remapping of all surrogate keys

Hi SSIS Engineers: Forgive me if this is a multi-forum question. Our primary activity in the next week is to automate the processing in SSIS, where I led the team to create complete processing flows for Full and Add in the order of Dimension, Measure Group, Partition, Cube, Database. These work. The problem occurs in a complete refresh of the ERP database that caused me manual effort inside SSAS, which I plan to find a way to automate in SSIS. I performed a complete refresh of our cube from the ERP source from a time perspective. We are automating this process in SSIS. In SSAS, I had to manually delete the four dimensions from the UDM view via the Solution Explorer. Since the complete refresh increased the surrogate keys in the dimensions and since the names were the same, I couldn't just drop the partition and reprocess the dimensions, since, in effect, new fact rows would have to be mapped to the new keys. SSAS held on to the old keys even with Full Processing of the Dimensions first, then the Cube. Until I dropped--deleted-- the dimensional tables from the Solution Explorer and the UDM then later readded the dimensions with the new surrogate keys (both add, update and delete dimensional attribute changes in full refresh) via the Add Dimension wizard, the cube kept the old surrogate keys and failed in measure group, fact, database and partition processing.

Need to Automate in SSIS Cube Drop and Recreate of Dimensions: Had to do on the Solution Explorer Ma

Hi SSAS Engineers: This question is in the context of a complete refresh of the SSAS cube. I'm OK on the SSIS approach thanks to TMcD and past successes (also thanks to him). The question is why did I have to manually drop/delete the dimensions in BIDS SSAS, then readd them with the cube wizard to pull in the dimensions with the same names, but new surrogate key relationships and more surrogate keys in total? We need to Automate in SSIS Cube Drop and Recreate of Dimensions. I originally had to perform this function on the Solution Explorer Manually in SSAS UDM, since the names are the same, but the structures and the data are changing for the dimensions on the refresh (and the fact table is subsequently increasing). Herein lies the problem. We had a keynotfound error in the cube processing, since the old keys were being kept. I had run Full processing on the dimensions, but since the dimensions have the same name (no drop old names and add new names), the old surrogate keys remained. The fact table had the old row count as well, since the surrogate key pipeline to look up the surrogate keys for the new dimensions only had the old dimensions, even though I truncated the fact table. Yes--I had already rebuilt the dimensions in SQL Server and the row counts were the new refresh row counts. The dimension counts were right according to refresh numbers after

Error while processing the cube

Hi All,  I am trying to execute a cube using the xml script. Below is the error what I am facing.   Message Executed as user: NT AUTHORITY\NETWORK SERVICE. ...s="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults"><root xmlns="urn:schemas-microsoft-com:xml-analysis:empty"><Exception xmlns="urn:schemas-microsoft-com:xml-analysis:exception" /><Messages xmlns="urn:schemas-microsoft-com:xml-analysis:exception"><Error ErrorCode="3238002695" Description="Internal error: The operation terminated unsuccessfully." Source="Microsoft SQL Server 2008 Analysis Services" HelpFile="" /><Error ErrorCode="3238002695" Description="Internal error: The operation terminated unsuccessfully." Source="Microsoft SQL Server 2008 Analysis Services" HelpFile="" /><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: [DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.; 08S01." Source="Microsoft SQL Server 2008 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'IA DIST VEH VOL A1', Name of

cube deployment fails- A duplicate attribute key has been found when processing

I am trying to create a cube using the same process that I always do. however this time I get an error message "Warning 4 Errors in the OLAP storage engine: A duplicate attribute key has been found when processing: Table: 'dbo_ALL_ResultsNewest', Column: 'MktCapGroup', Value: ''. The attribute is 'Mkt Cap Group'.  0 0 
This is using alot of data but I have created similar size cubes before. I create simple cubes with a single dimension and all the attributes related to a single master attribute. I am a data analyst, not a technologist and don;t have any real understanding of cube internals beyond the basics.

0x80040154 error processing a cube from SQL Server 2008 R2 x64 database engine to OLAP Server 2000 x


I recently upgrade from SQL Server 2000 x32 to SQLServer 2008 R2 x64 but only the database engine not the Analysis Server, I used to use this code to proces the cubes.


but now it do not  work more with the error:
Error at create server:
Error      Source                    Description          HelpFile HelpID
---------- ------------------------- -------------------- -------- -----------
0x80040154 ODSOLE Extended Procedure  Clase no registrada NULL     0

(1 row(s) affected)

I found this article:

It means that I can not process the cube using the same method any more ?

New DSV named query or copy and reuse an existing cube dimensions (is the latter valid) - SSAS 2008


I have a [DateAsAt] table in the DSV. This is linked to 3 fact tables to analyse and slice them from an as at date perspective (lets call them FactA, FactB and FactC). But I want to reuse this dimensions (almost like an alias) and although I have tried this and it seems to work, I just want to follow some due dilligence to make sure what I am doing is valid.

I have not created a new Named Calculation for a new date dimension that will be used in a Transactional way (not an as at way), and in stead simply copied the [DateAsAt] dimension, and pasted it back into the dimensions section of the cube (the default name it was given was [DateAsAt 1], but I changed it to [DateTransaction].

Although the relationship between the [DateTransaction] dimenion's source in the DSV (I.e. [DateAsAt]) is linked to FactA, FactB and FactC, I set a new dimension relationship between [DateTransaction] and FactTransactionD in the Dimension Usage area of the cube.

Is this valid? or MUST I create a seperate source for [DateTransaction] in the DSV and set its relationships there?

XMLA for Cube Processing fails when called from SQL Agent Job


I have some XMLA which runs fine in SSMS, but fails when called as a step in an agent job. Here is the XMLA:

  <Process xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">

And here is the error from SQL Agent:

An exception (0xe0434f4d) occurred in the ANALYSISCOMMAND subsystem.  The step failed.

I am running this on SQL 2005 SP3 Developer Edition. I have even tried uninstalling and reinstalling the instance. The PC also has SQL 2008 instances installed (I'm not sure it that is relevant or not). I can get the SQL Agent job working fine on SQL 2008 and another SQL 2005 box.

Can anyone help?


dimension's incremental process generates processing on all partitions in cube


Hey eb

Have any one noticed this behavior??

Incremental process (process update) of dimension generates reprocessing of indexes on all cube's partitions,even when no change has occured in that dimension.

I am using SSAS 2005 sp2.

This is disturbing because my cube holds some 700 daily partitions so processing indexes on all of them - on an hourly basis - is very time consuming.

Also it flashes that cube's cache!


I did noticed that changing heirarchies memberskeysunique property to True + changing the toppest attribute in this heirarchy mambernamesunique to true solves this problem.

Is this a must then to prevent recalculating indexes on partitions every process update of dimension??



Alter measure group: Impact on cube processing?

Hi All,

I have a XMLA script to alter source column (<ColumnID>) of a measure. I would like to know
following regarding the script:

1 - Do I have to 'Process Full' the cube or other processing options are applicable?
2 - The cube takes 2 hrs to process. Will there be reduction in process time processing the cube
    after running the script or will it take the whole 2 hrs?
It running cube on production so I would like to minimize the impact of the alter script.

Thanks in advance for any help.

Processing SSAS 2008 cube using third party scheduler

What are the different options to process SSAS 2008 cubes automatically using third party scheduler? What is the most recommended approach?

Cube Processing Taking Random Timings every day.....



I have a question which i am facing from long back...

My question is...

our Business System has a cube which is processed daily morning.

It should take around 1.30 hours to Process this cube. But its not the same every day.

I wont bother if it takes a little bit more than that, but its taking different timings every day.

one day its around 2 or 3 or 5 or 7 or sometimes its going to around 10 also.

i am really suprised to see why the same cube on the same server is taking such a huge difference in timings everyday.

Can some one Explain me what i need to do to make the timings not to go too long.


Deadlock for a cube processing - SSAS 2005



I have a scheduled job with a step that calls a cube processing. This job run daily. Some times the processing stops for a deadlock. I have seen that when the processing overcomes 60-70 minutes a deadlock occurs. Is it possible that any settings for the Analysis Server instance can affect to the deadlock occurence?

Many thank for your helps.

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend