The report manager will definitely not allow such report rendering. Least you will have to design a custom reporting client for your purpose. This is easy!!

This is a welcome resource..

Click here

You have a file...file has records...you have a table...insert data into table...game over!!

The discussion boils down to the following:

1. One cube with sparse facts

2. Multi-cube with relevant facts

You know that was a joke...

Anyway, nice to see that you are engrossed in self pace study...

I would highly recommend that you gain a strong hold on DW principles first,...

Can you be a little specific?

Substantial is a very vague term.

How about a quick round of revision?

Rate your self in DW concepts and OLAP on a scale of 10?:-)

having all sorts of measurable data in one pot(cube) is bar far a bad practice....kudos to performance management

You may consider specific cubes creation for specific reporting solutions.

It largely depends upon the factors that the business considers while designing the KPI's.

A business could very well measure KPI for freight as freight/tonnage(this is an arbitrary example)

This is a...

Jez,

A multi-fact table is a better approach. A fact table with sparse data will hamper the record retrieval process.

steveb. (4/13/2011)

---

100,000

from the Indian numbering system, quite common depending on where and who you work with...

http://en.wikipedia.org/wiki/Indian_numbering_system

As for the formatting...

This should do the trick!!

=Format(Fields!Price.Value, "#,##0.00")

Moderators,

Please mark this post as a spam and request you to close this thread.

sdhan79 (3/3/2011)

---

Thanks Raunak Jhawar. I didn't list any reference between fact table and dimension. As for the two different fact table, I think you are right :). ...

Superb!!!