Viewing 10 posts - 1 through 10 (of 10 total)
Dimensions and fact(s) data are internally represented in terms of flat files, atleast in msas 2000. Should be the same in SSAS2005 ..
April 15, 2009 at 11:35 am
Thanks for the reply. Yeah, I am now using DTExec. Following is the progress on this:
I have the dtsx file and the batch file that calls this dtsx...
April 2, 2009 at 8:55 am
It may be pretty complicated. The problem may be because of having overlapping weeks accross month(s) and year(s) etc..?!
May be u can think of having week start date, week...
July 7, 2008 at 3:34 am
Try this function in the MDX using WITH Member clause,
Sum({ClosingPeriod([Time].[Year - Trimester - Month - Date],[Time].[All Time]).lag(15)},([Measures].CurrentMember))
where 15=filtervalue ie., before 15 days for example.
July 7, 2008 at 3:26 am
Actually, I am working on the MDX query. Since it looked to be a real huge effort as you say, wanted to check if there is any different way...
June 11, 2008 at 8:30 am
Old and New are AS 2000. The old cube has all 2 years of data. The data source tables (SQL SErver 2000) corresponding to the cube gets backed...
June 11, 2008 at 6:51 am
Okay..Actually I am working in MSAS 2000. Is that something specific to 2005 version?
June 11, 2008 at 6:47 am
Yes, there can be a schema problem.
After the partition processing complets, extract the query that gets generated and used for partition processing and execute the query from SQL...
June 11, 2008 at 12:53 am
Michael,
We decided to drop the aggregations designed for now as it was taking much resource. By the way, I don't find an option to set the attribute relationship...
June 11, 2008 at 12:20 am
Mark,
Did you fix this issue?? I have a similar problem here. I have 3 changing dimensions on my cube and the cube has around 200 partitions sliced at...
May 19, 2008 at 10:03 pm
Viewing 10 posts - 1 through 10 (of 10 total)