+5  A: 

Why are Production and Sales are in different schemas?

On the assumption that they just are, and you can't change that -- put it in whatever schema is responsible for the bigger perspective share. Meaning, if your question is usually "who is responsible for selling product x?" -- it should go into Production. If it's more of the "what product does salesperson x sell?" -- it should go into Sales.

This is kind of a screwy design imho, for the very reason of cross-schema relationships not having an obvious home (but if there are good reasons for setting things up this way, I would appreciate being enlightened).

SquareCog
(1) I'd guess it belongs in Sales, since it seems more an attribute/description of a salesperson than a product.
Philip Kelley
(2) Adventureworks is a sample database, designed to show of the myriad features of SQL Server 2005. As such, I'd have to guess "proper design" came second.
Philip Kelley
@SquareCog: "what product does salesperson x sell?" -- it should go into Sale <-- That is what makes sense to me in this case.
Sung Meister
+1  A: 

In real life there would be a user to ask. But if we have to guess, it is normal for sales people to be assigned products as their beat, and the responsibility for that decision is taken by Sales rather than Product Development. So I would say that your intersection should belong in SALES rather than PRODUCTION.

APC