Re: DB design for a multible company accounting system
> create 20 tables for every company (40.000 tables), for example table
impossible to maintain
> using partitioning with companyId as separator
not what partitioning is for
> only split the 3 big tables (6000 + 17 tables)
awkward
> just use 20 tables with companyId as part of key
the fundamental idea is to minimise redundancy, so yes
Subject
Written By
Posted
December 16, 2014 02:19AM
Re: DB design for a multible company accounting system
December 16, 2014 12:00PM
December 17, 2014 06:54PM
December 18, 2014 08:44AM
December 18, 2014 04:42PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.