Application Db Design guideline for multiple applications on same platform
Posted by: Nikhil Kapoor
Date: August 06, 2007 05:58AM

Hi,

For a project we are required to build multiple applications. Now each of these application requires set of data tables as part of thier respective data model, besides there is some common data which is to be shared with different applications.

The issue we are facing is how should we model the dbase - the options are:
1. Build one big database where tables related to each application resides in same database. thus if there are 20 application with say 10 tables then we will have big database of 200 tables

2. Build individual database for each application thus in above scenario we will have 20 databases with 10 tables each. For the master data we could make a separate database

The first option does not give neat model and also we can not define dbase wise securty so are leaning towards 2nd option. However not sure how in this option we can apply foreign key contraint where required. Would MySQL support defining foreign key constraints in this manner - if no how should the model be prepared.

An option is to define triggers on tables to ensure data integrity - is that advisable?

Also if we were to adopt option 1 - does it have any perfromance or other deisgn disadvantages?

I would appreciate any help in the regards,

Nikhil

Options: ReplyQuote


Subject
Written By
Posted
Application Db Design guideline for multiple applications on same platform
August 06, 2007 05:58AM


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.