Lazarus
Free Pascal => Database => Topic started by: Almir Lima on March 08, 2018, 02:09:35 pm
-
Hi, everybody.
Whats is the better pratice to model DataBase.
More tables or mor fields in tables?
Why?
-
I'm not a database expert, but I ever knew database normalization:
https://en.wikipedia.org/wiki/Database_normalization#Normal_forms
-
In theory more tables and less, but related columns. This is the so called database normalization. The model assumes infinite computer power, which unfortunately is never true, so in reality use less tables with lots of columns. Ideally you should start with a perfectly normalized database and watch how miserably fails as data grows, but then you have to rewrite the whole thing and it hurts. Don't do it.
-
GetMem is absolutely right. Usually normalise to level 4 (fourth normal form) and then go back to level 3 and take into account any small optimisations that may be worthwhile.
-
There is a large biography you could learn from.
I will suggest you some of the same books I always suggest to my students start from:
The Manga Guide to Databases | Illustrated
by Mana Takahashi and Shoko Azuma
Jan 15, 2009
Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition)
by Michael J. Hernandez
Feb 14, 2013
Database Design and Relational Theory: Normal Forms and All That Jazz (Theory in practice)
Author: C. J. Date
Apr 27, 2012
SQL and Relational Theory: How to Write Accurate SQL Code
Author: C. J. Date
Jan-2012
Database Systems: Design, Implementation, & Management 12th Edition
by Carlos Coronel, Steven Morris
Jan 26, 2016
Database Systems: Introduction to Databases and Data Warehouses
by Nenad Jukic and Susan Vrbsky
Jun 2, 2016
Project Management Analytics: A Data-Driven Approach to Making Rational and Effective Project Decisions (FT Press Project Management)
by Singh Harjit
2015-11-16
Database Reliability Engineering: Designing and Operating Resilient Database Systems
by Laine Campbell and Charity Majors
Oct 26, 2017
-
Thanks for replying