If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > General > Database Concepts & Design > Separate Database or Schema

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 08-14-04, 06:17
rkjoshi rkjoshi is offline
Registered User
 
Join Date: Aug 2004
Posts: 1
Smile Separate Database or Schema

Dear All,

We have developed and deployed an ERP in a pharmaceutical company. Now a separate division has been created and has the applicability of most of the modules in the ERP but with 10 - 30% dissimilarities in the business processes. I am heading the project and in a Dilemma.

Pls. guide me on the following -

1. When should we create a new database.
2. When should we create a new schema.
3. When should I add a new table in the same schema.
4. When should I add additional columns in the existing tables.

Thanks

Raj
Reply With Quote
  #2 (permalink)  
Old 08-14-04, 11:26
Pat Phelan Pat Phelan is offline
Resident Curmudgeon
 
Join Date: Feb 2004
Location: In front of the computer
Posts: 12,605
I just love RFH postings!

1) Add a new database when the boss tells you to
2) Create a news schema if there are seven or more tables in your present schema
3) Add a table to the existing schema when a new entity is added to your application (but also see #2)
4) Add new columns to the tables when the columns that exist won't hold new data.

-PatP
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On