TM1 Forum

I have been trying to generate a snapshot(using cubeviewer), but it is taking longtime(approximately 20 mints),total records in snapshot is 350000 records.Is there any way to reduce the time to generate snapshot?Cube having 18 dimensions
Note: Cube has taking one min time to generate a required view
Environment:
TM1 10.2
Excel 2010
windows server 2008 R2

Do we have any limitations to generate a snapshot or slice or active form?
Could you please suggest on this.

Thanks,
Chowdary

svchowdary83 wrote:I have been trying to generate a snapshot(using cubeviewer), but it is taking longtime(approximately 20 mints),total records in snapshot is 350000 records.Is there any way to reduce the time to generate snapshot?

Yes; by recognising that 350,000 rows is NOT a snapshot, it's a data dump. You should therefore be exporting it to a text file. If you want to bring it into Excel for further filtering that's fine but you'll get no value out of having Perspectives pump it directly into an Excel sheet with all of the overhead that that entails.

svchowdary83 wrote:I have been trying to generate a snapshot(using cubeviewer)....total records in snapshot is 350000 records...........Cube having 18 dimensions

A cube of 18 dimensions will be cumbersome, confusing and not easy to use.

Why are you trying to snapshot the data, is it so the end-users can manipulate the data in Excel? If so maybe you should look at a better way of doing it within TM1

svchowdary83 wrote:I have been trying to generate a snapshot(using cubeviewer), but it is taking longtime(approximately 20 mints),total records in snapshot is 350000 records.Is there any way to reduce the time to generate snapshot?Cube having 18 dimensions
Note: Cube has taking one min time to generate a required view
Environment:
TM1 10.2
Excel 2010
windows server 2008 R2

Do we have any limitations to generate a snapshot or slice or active form?
Could you please suggest on this.

Thanks,
Chowdary

Posts like this make my head hurt. (I should probably stop slamming my head into the desk when I read them.) I'm happy to debate anyone who believes they have a legitimate reason for slicing or snapshotting out thousands of rows of data (or more).

I've seen this before and virtually every time it's a user training issue. They're probably taking the numbers out then using power pivot to slice and dice the data. Even this thought will probably make your head hurt even more Lotsaram. Might I suggest an inflatable desk??