Outsource customer specific objects
714112Nov 25 2012 — edited Nov 25 2012Hi,
the more customers we have for our software solution the more individual oracle objects (Tables, Packages, Functions, etc.) we have in our scheme.
Right now we separate these by giving them identifying names like "X_CUSTOMER1_TABLENAME" e.g.
This is not very practical when keeping our reference clean and when deploying/syncing our reference with a customer db. One customer would receive the objects of other customers.
Is there a common solution to this problem? We were thinking about having a separate scheme for each customer. That wayy we ould have our standard, untouched scheme with the basic functionality and the customer schemes with the individual content.
I would appreciate any hint or best practise.
It's an oldschool relational db.
To make it a bit more concrete: We have around 100 basic tables that make the most of the content/functionality of the software. Each customer might have between 1 -5 additional tybles with "custom" data that is brought together through individual packages, functions etc.
Most of the time only this customer will have these 1-5 tables (company internal content that does not make sense for any other company).
Thank you!
Edited by: user7403338 on Nov 25, 2012 4:26 PM