Is there a rule of thumb for including the value of a foreign key in a table to avoid large joins?

Databases: Is there a rule of thumb for including the value of a foreign key in a table to avoid large joins?

Helpful? Please support me on Patreon: https://www.patreon.com/roelvandepaar

With thanks & praise to God, and with thanks to the many people who have made this project possible! | Content (except music & images) licensed under CC BY-SA https://meta.stackexchange.com/help/licensing | Music: https://www.bensound.com/licensing | Images: https://stocksnap.io/license & others | With thanks to user Seb3W (dba.stackexchange.com/users/88819), user Pierre Nortje (dba.stackexchange.com/users/104254), user paparazzo (dba.stackexchange.com/users/14476), user Andy Jones (dba.stackexchange.com/users/50765), and the Stack Exchange Network (dba.stackexchange.com/questions/147713). Trademarks are property of their respective owners. Disclaimer: All information is provided "AS IS" without warranty of any kind. You are responsible for your own actions. Please contact me if anything is amiss at Roel D.OT VandePaar A.T gmail.com

answerdatabasedatabases