@Charlieface I don't mean to attack. Sorry about that. I was trying to pedantically correct your pedantic correction (which was incorrect, or at least irrelevant).
> As an aside, I also think it is worthwhile to name your primary identifier in full (e.g. Products.ProductID instead of Products.ID) so that the identifier is consistently named throughout the schema.
No, there is no value in adding an additional "primary key" to this table. Your joins are only ever going to refer to ProducerID and ProductID, so it is just dead weight. IMHO.
Though I agree with @Shark that the join table doesn't even seem to be needed here, unless you are going out of your wa...
@Yano_of_Queenscastle — thanks for the assist. Turns out I didn’t have it installed. I had assumed that starting with SQL Server 2012, sp_BlitzLock was included by default on the instance. — DevOpsLens20 hours ago