TM1 Forum

Hi all,

Hi all,
Should i built dimension same below struture

Year all
Year 2014
Jan 2014
Feb 2014
Mar 2014
Apr 2014
Year 2015
Jan 2015
Feb 2015
Mar 2015
Apr 2015
v.v.v.v

I am use struture calculation depreciation year by year. It effect speed load data cube.

Thanks you so much

If you would read this question a second time, would you be able to understand it? I'm not, sorry.

I'm sorry, but I doubt that anyone has the vaguest idea of what you're asking here. Let's try for some specifics:

ChauBSD wrote: Should i built dimension same below struture

Year all
Year 2014
Jan 2014
Feb 2014
{Etc}

This sounds like a pretty typical single time dimension design. Why do you feel that it may be a problem? When you ask whether you should build it, what alternatives are you considering and why?

ChauBSD wrote:I am use struture calculation depreciation year by year.

OK, but what does that have to do with the structure of your time dimension? Obviously the rules that you'll use will vary depending on how your time dimension is structured, but have you actually created those rules? If so, what are they? What are the feeders for them?

ChauBSD wrote:It effect speed load data cube.

What affects the speed of loading the data? What data are you referring to? Why do you feel that the time dimension hierarchy has an impact on the load time, if indeed that is what you're claiming? As they say in the Request For Assistance Guidelines, "Try to make the question as specific as possible."

(I see Wim beat me to it, but what the hey, I'd already typed the reply. I agree with him, though; try reading the question from the point of view of someone who isn't you and doesn't know what you've been working on. You'd have no chance of figuring it out.)

Hi all,

I just wanted to get your advice. I have dimension Times with structure same image. With structure such a long time that affect data speeds when load cube.
Cause, i am used structure because i wanted calculate asset depreciation and project management through the years.

Thanks you so much.

Do you mean that you have feeders in place that feed from a single month to the entire future? The year 2031 in this case?

... or is it that you have a calculation that is iterating over previous (or subsequent) periods to calculate each period value?

If so then the performance will depend greatly on whether the calculation deals entirely in numeric cells (in which case they will be cached) or string (in which case they won't).

If it is a rule then share it and the rest of the community will understand better what the situation is.

Do you mean data loading as in running a TI process and CellPutN function loading leaf data to the cube or do you mean "data loading" as in querying a view and waiting for the view to load? Quite different things. If it is real data loading (the former) then dimension structure is pretty much irrelevant, the only thing that slows down data loading is firing lots of feeders upon data entry (especially if recursive and feeding from/to consolidations). If it is slow query performance then quite a bit more information is needed. Either way if you want help you need to specify what you mean by data loading and post some detailed information about your rules.