Quote:
Is there a db design standard of using different table for different data type?
Databases design is more than the structure of data, its usage matters too.
Example:
- your company have a databases of orders. 1 table look enough.
But you have a process that continuously need to know active orders because it try to reduce waste (steel beam stock cutting).
Chances are that continuously filtering the global database to active orders will be more resources hungry than handling a secondary database with only active orders.
In this case, duplicating data tables will be more efficient because of the usage.
Other considerations can enter into account.