Hey Brent and crew -- always love this channel. Question: Would it be more effective to create an "ages" table (AgeName | AgeStart | AgeEnd) and join to the "dates" table to reduce the repetition of the field "Age of Goats" in the date table column for the ~90ish days that are included therein? Is it more performance intensive to include more joins and therefore better to just include the "DateAge" column in the dates table? I'm new to query tuning! Thank you! :)
![[Part 1] รักมาไม่ทันตั้งตัว❤ หนุ่มสาวโสดถูกจับมาแต่งงานกันกะทันหัน แถมเธอยังเป็นหัวหน้าของเขา?!](http://i.ytimg.com/vi/y2pOOMkuFI0/mqdefault.jpg)
![🔴 ฟุตบอลแชมป์กีฬา 7HD แชมเปียน คัพ 2024 [รอบ 8 ทีมสุดท้าย] - ช่วงบ่าย](http://i.ytimg.com/vi/M0S_ReCIkxg/mqdefault.jpg)
3:00 awesome, i was just working on that problem today, wanted to show 0 even though ID didnt exist in the table!
Hey Brent and crew -- always love this channel. Question: Would it be more effective to create an "ages" table (AgeName | AgeStart | AgeEnd) and join to the "dates" table to reduce the repetition of the field "Age of Goats" in the date table column for the ~90ish days that are included therein? Is it more performance intensive to include more joins and therefore better to just include the "DateAge" column in the dates table? I'm new to query tuning! Thank you! :)
Thank You! Very informative.
I believe this is called a tally table. It is spectacular for string operations
That's another word for 'em, yep - make sure to watch the video before you comment, because that's covered in the course. Enjoy!