design approach for ERP database -
i must re-build erp app did 7 years ago. old database design was: 1 document -> 1 table. example: invoices have there table.
i search other's database design, such openbravo , did similar.
this kind of design has advantages:
- makes easy search (directly) database
- in case of mistakes, table involved
- other...
but nowadays things different. databases mongodb scene make me doubt. other possibility, make 1 big table kind of documents. so, example, using single table inheritance can store different document data on own.
this approach dive me 20 tables 1 childs. final question is:
should design one-document/one-table or should go oo design 1 general table?
note: commercial/financial documents, db has other tables other concepts.
i don't think able precise answer other this:
it boils down needs. need choose database software , technology according needs. there many , each tool not @ of them. points need think about:
- how data need store ? gigabytes ? hundreds of gigabytes ? terabytes ?
- how many users need access database @ same time ?
- do need able / replicate data across multiple servers ?
- is data structured or more flexible ?
- what experience of company various database software ?
- how company going invest in project ?
- do need support acid transactions ?
those questions should answered before pick tool "because know it". erp piece of software critical enterprise suggest give lot of thought specific technologies considering , why making onto list. when know should pick tool best fits criteria.
Comments
Post a Comment