I have system user id set as aa fact. What would have if i leave it so. How does is it bad for reporting.
I beleive if i leave it as a fact then when i drag drop it into report studio it would be aggregated. Which would mean that i could have wrong number against system user id in the report, if their is aggregation in the report.
Second, the query subject would be considered as a fact by the engine even if it has only dimensional information, which means bad results.
Is there any other?
If an identifier is set as a fact, which happens all too often, the following happens:
1. It is not used to group by. That means that if you pull the identifier (In your case, user ID) and a measure (Say you want to see total logon time for a user), you won't get the data per identifier.
2. The identifier aggregates. You pull user ID, you get one row - the total of IDs. That's never a good idea.
Quote from: dssd on 27 Aug 2011 04:04:05 PMSecond, the query subject would be considered as a fact by the engine even if it has only dimensional information, which means bad results.
This is not the case. Query subject identification is done based on the cardinalities of the relationships used in the reporting query, not on whether items are labelled as fact/identifier/attribute. The rest is as Nimrod says - I would heed his wise advice. :-)
MF.