The ability to allow custom fields to be added to a database is a common requirement. This could be something the user wants to add when using an application, or for defining reports, or something else. There are many different ways of allowing custom fields in your database design. There is no one right solution though, as it depends on your requirements, amount of data, and the application. In this video, I'll share 8 different solutions that can achieve this requirement. Each of them has a sample diagram to help visualise it, and a list of the advantages and disadvantages. The solutions are (with timestamp links): 1:52 - EAV (Entity Attribute Value) 5:17 - Modified EAV 8:06 - Single Table 10:34 - Class Table Inheritance 12:21 - Concrete Table Inheritance 13:36 - Normalised Tables 15:09 - JSON 16:34 - Dynamic Schema Hope you enjoy the video and find it useful! /// RESOURCES 📝 Get my free SQL Cheat Sheets: https://www.databasestar.com/get-sql-cheat-sheets/ 🧭 SQL Roadmap from basics to advanced: https://www.databasestar.com/sql-roadmap/ ✍️ Learn how to design a database: https://databasestar.mykajabi.com/edd 🎓 Improve your SQL and database skills with Database Star Academy: https://www.databasestar.com/dsa/ 📧 Contact me here: https://www.databasestar.com/contact/ 📝 Database Design Exercises: https://bbrumm.gumroad.com/l/hqsxi 📝 SQL Practice Questions: https://bbrumm.gumroad.com/l/ulekqk 📝 SQL Performance Quick Guide: https://bbrumm.gumroad.com/l/fcvny 📝 Ultimate SQL How-To Guide: https://bbrumm.gumroad.com/l/oqggau