when stitched query is created and it is good for performance or not

[inu]

Hi
As i know stitched query is created when two fact tables and one dimension table. But i want to know stitched query is good for performance or not. creating stitched query is good or bad for our report.



Thanks
Inam

[Lynn]

If you are attempting to report on two facts across conformed dimensions then a stitch query is necessary. It can be done efficiently. Separate queries will be issued to the database and the results will be combined locally as a full outer join. Of course there are numerous factors that affect performance depending on the quantity of data being combined, configuration of your particular environment, database performance of the separate queries and so forth.

If, however, stitch queries are being generated because of improper cardinality in the model then it is a very bad thing indeed.

You need to understand your reporting requirements and your data to really determine if good or bad things are happening. Are you able to identify an alternative to a stitch query that will provide correct results? If so then I'd suggest it may not be a true multi-fact query scenario.

I don't think there is a simple answer to your good/bad question.