Re: A Database within a Database?
Alternatively.
Have one Table 'Jobs'. When a new Job is created, all new tables are created under it. I dont really need to share anything. Can start entering parts from scratch easily by importing from a spreadsheet at the beginning of every job.
Just want to make sure that when we are working under a Job, there is no need for the DB to call any huge tables that have developed after years of usage.
Additionally, I dont even want the Products tables to be shared.
A clean DB as a new job or project is created is a cleaner solution.
Subject
Written By
Posted
Re: A Database within a Database?
June 01, 2015 08:57PM
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.