I've got a data normalization question, about possibly redundant foreign keys. I have a table [Jobs] that has many [JobValues]. [Jobs] also has many [Orders], and [Quotes]. A "JobValue" not only belongs to an "Job" but it also belongs to a "Order" and/or a "Quote". My [JobValues] table has a foreign key for "JobID", [Orders] and [Quotes] are directly referenced to [JobValues].
My Question: Should my [Orders] and [Quotes] also have a "JobID" field OR should my queries on [Orders] and [Quotes] reference its associated [JobValues] to look up its "JobID"? Or is this all just a matter of preference?
Notes: [Jobs] -> [JobValues] is kind of the core of this database. I'm fairly certain I at least need [JobValues] and [Jobs] to be directly related. The examples in this post are quite slimmed down from the actual DB.
Do like this?
Or like this and use query magic to find a Quote's Job through it's JobValues relationships?