a problem when I
process a cube
SSAS 2008, I
a SSIS package
View Complete Post
I have an analysis services project in Visual Studio, and now I added a column to one of the tables composing the dimensions (it's a MOLAP DB) and made it the primary key, and then I updated the tables composing the measure groups by deleting the key field
to the dimension table and replacing it with a field that refers to the new column in the dimension table. The problem is that when trying to deploy the changes, I get errors for the measure group tables that say the data source view doesn't contain a definition
for the old column that I deleted and thus of course is not supposed to be there. Why can't it identify the change and process it correctly, and what can I do?
I need to dynamically generate a list of images in table format. The images can be found in either art or picts, in temp, or in temp and in one of the other two (duplicate image).
The idea is to display any duplicates prior to copying anything over from temp to either art or picts, so I'm thinking of adding radio buttons if the same image is found in two folders. I also want to add a submit button. The user selects the image they want and clicks the button. If they want the new file it's copied over then deleted. If they want to keep the existing file the new one is just deleted. If they select nothing, both versions of the file are deleted. So the table will look something like this:
temp art picts processz-123 delete button() z-234 () z-234
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
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?
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 ?
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??
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.
Got a problem creating cube using AMO.
I am using a table which holds the dimensions and measures I want in my cube.