Re: Table naming conventions

Don - Your answer depends on various unknowns:

But as a rule (standard) it is best practice to always pre-fix your object with the schema it belongs to (as in your options (3)).

If you want to avoid database links then you'd want to keep the tables within the same instance. But, seperate instances mean easier maintenace for DBA purposes as they can be administered seperately and DB parameters can be set independantly for different application that may have completely different characteristics ie. on-line real-time vs. batch over-night processes.

If you wanted to easily differentiate between your own 'application' and client 'applications', then a prefix on object names seems a reasonable rule, as it makes the objects immediatelly identifiable.

Regards

• Martyn Cavett Senior ORACLE Analyst LGT Asset Management London, UK. home: cavett_at_globalnet.co.uk work: Martyn.Cavett_at_gtplc.com

These views are my own and not those of my employer. Normal conditions apply.
nb. anonymous return address used - please replace reply address with those given above. Received on Mon Aug 18 1997 - 00:00:00 CDT