I'm working on the DB while others work on getting the data together, and the Stress data has not been recorded/extracted yet.![]()
I have RawDetails and ExactDetails because the stresses will be coming from lots of different documentation. One doc might say "300ft/lbs of torsion caused failure", and another might word things differently and say "failure occurred after 300ft/lbs of torsion". That will go into the RawDetails, whatever the document listed as is. ExactDetails will be a field with some sort of standardization for that particular type of stress, likely a number with some text.
I'm keeping things vague for privacy, but basically the db is cataloging parts, and the parts have failure rates/methods associated with them. (Plus lots of other data.)
Yes, ItemID and StressID are compound PK on this table, and the ItemID is linked to another table of parts. That way each part can have multiple stresses. (Actually, now that I'm looking at my relationships in the DB, I have 3 tables. The Stresses table, the Item table, and a table in the middle that associates them. I guess that kind of over complicates things on my table design.)