Joining to two One-to-Many tables - should be simple

  • Peter, thanks again.

    Happy Veterans Day!

  • Ed Srdoc (11/11/2010)


    Correct. Since the two don't relate to each other, the order is insignificant.

    I'm just thinking about how a user report would look.

    I'd expect a user report would be built on two sub-reports.

    One would query the relationship between families and children, the other between families and cars.

    Had something similar come up with a project management system we've developed in house. Source systems for data and Services rendered on the project. User wanted to know why they couldn't pull it all together. Fortunately SSRS report models prevented it. Showed the user how to create sub-reports for this sort of info and explained that until services rendered on a projet had a relationship to the source system, they wouldn't be able to pull the two together.

    Another simpler approach would be to give them back two sets of data. If they're doing a report they should be in two seperate sets of rows/columns as otherwise you're implying relationships that probably don't exist.



    --Mark Tassin
    MCITP - SQL Server DBA
    Proud member of the Anti-RBAR alliance.
    For help with Performance click this link[/url]
    For tips on how to post your problems[/url]

Viewing 2 posts - 16 through 16 (of 16 total)

You must be logged in to reply to this topic. Login to reply