Optimal Design
Hi All,
This approach consumes lot of space. Please can you suggest any other Optimal methods.
Regards,
Rajsekhar
Answers
-
To begin with having a file of 40K records is perfectly alright and not that big a deal. But you have to make sure that you are loading just the items in SKU list and create a SYSTEM module to hold its other associated properties instead of loading them as List Properties. Having those properties as text or list - I would definitely go with the list formatted line items.
1. Now how do you load the other lists? Do some analysis and see if all these list items change over time/frequently, if not you can mark these as non production lists and create it one time upfront and forget about it. If these are supposed to be production lists then yes you have to load all these lists one by one before your upload the file.
2 Reducing the size - This one is a big topic....but in this case you can keep your summary off for all the line items.Don't make this module multi dimensional module, it should only be dimensioned by SKU list
3. The question is do you want all these three lists as dimensions. Think about it, if for every A+B+C intersection there be a unique value then I would say you need all the three dimensions and if not then you can probably get rid of B or A because there is a connection between these two already, you won't be having any difficulty to aggregate the data
Misbah
0