I am working on upgrading and redesigning logic and data involving weekly delivery schedules.
We have thousands of vendors, delivery schedules, manual interventions, so my redesign would mean the schedule table could quadruple in row count but would allow granular adjustments.
Both ways work fine, but what is best terms of best practice?
Is this anything to do with normalization/denormalization, is normalization important here? And if normalization is important, which method is more normalized? Or am is this just a matter of opinion?
There are no universal best practices. Do what makes sense in your situation. For example, what's more valuable to you: saving disk space and having complicated logic or paying the disk price for clean logic and easy updates?
Disk space is cheap (and can be unlimited), time* is more expensive and is limited. Your call.
(* developer salary, time to market, time spent on debugging, etc.)
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.