Good morning!
I've been working on building a QA database for the brewery I work at. We have several sets of data collected for each batch of beer, collected at different points along the brewing process.
I'm running into issues with table design - which I'm surprised at to be honest.
The only data point that connects each set of data is a batch ID, so I've chosen that as the primary key.
The problem is, as you'll see in my attached relationship map, is that I have duplicate columns in each table and I'm not sure the best way to eliminate them.
Open to all ideas, it's functional as is but will quickly become non-functional.
Many, many thanks!
Jeremy