Re: Lookup tables in multiple databases?

On Aug 14, 9:48 pm, grawsha2..._at_yahoo.com wrote:
> Greetings,
> I have a question about "the best" approach to deal with lookup
> tables(employees, sections, etc..) that show up again and again in
> many database (HR, Inventory, CRM ) of an enterprise with Oracle DB
> servers.
> Should a separate database be created to include such lookup tables
> and have that database referenced on the front-end with the main
> database of the application whenever needed; Or have these tables
> created in databases, thus, one ends up with duplicate lookup tables,
> more or less.
> Interms of performance, scalablity and all issues of Oracle GP DB
> design??
> Any urls, books to help.
> MTIA,
> Grawsha

I don't know that I'd necessarily create an entire new database, but I'd at least designate an existing db to be the official database of all enterprise-wide data. Put it in its own schema. Then again, maybe I would create a database specifically for this. First rule: eliminate data duplication.

In the words of my first DBA instructor, "it depends." Received on Wed Aug 15 2007 - 07:51:14 CDT