Table Joins? DB or Conforming Layer?

[blom0344]

My 2 cents would be that the whole automatic 'Star-schema grouping' wizard is just that: a wizard. In purely functional terms you do not need it. It doesn't add anything valuable to the model at all. In other words : you can live without it just the same..

[tupac_rd]

My 2 cents would be that the whole automatic 'Star-schema grouping' wizard is just that: a wizard. In purely functional terms you do not need it. It doesn't add anything valuable to the model at all. In other words : you can live without it just the same..

I almost thought the same too, except that when we were on 8.3, if we would'nt use automatic 'Star-schema grouping', the query would choose the wrong path. But they fixed it since, I think starting 8.3 SP1 or 2 not sure.... So other than that reason, yes I agree we can live without it...

[RobsWalker68]

Hi,

I've always found it does very much depend upon the type of underlying data source you are acting with. 

If the underlying data source is a star schema with no snow flaking then we tend to make the joins in the business layer instead of the db layer.  For query predictability the 'as view' concept seems to make more sense.   On the other if you are operating against an operational source then perhaps minimised SQL would be of more importance and the joins should be made an the database layer.

Kind Regards

 
Rob