Just curious, but what in the world are your developers thinking? Literally, a million small tables? My suggestion is to fire at least one of the developers and hire a competent data architect as a replacement. (Probably doesn't matter which one you fire if they all think this is a good idea...:-o)
Performance would be poor, and I disagree that it would be any easier for them to develop using a data model with a million tables. However, a well-designed data model usually makes things easier for everyone.
CSL
>
> Luis Londono wrote in message <3730EA76.15F080_at_bigplanet.net>...
> >I need help with a littlle problem that I have. I have a bunch of
> >developers that want to create an application using Oracle that would
> >end up having probably a million very small tables (100 - 1000 records
> >each). It is easier for them to develop it this way, but I am trying to
> >convince them that it is not a good idea. It seems to me that the
> >performance of the entire database would suffer a lot since the data
> >dictionary would be over worked. Unfortunately I do not have any solid
> >evidence or an argument more convincing than a gut feeling. Does anyone
> >have some information that would help me? Or if I am wrong, I would
> >sure like to know. Thanks.
> >
> >-Luis
> >
> >--
> >Luis Londono
> >Senior Systems Engineer 370 E 1130 S
> >Big Planet Inc. Provo, UT 84606
> >mailto: luisl_at_bigplanet.net (801) 345-7222
> >
> >
>
>
>
Received on Sat May 08 1999 - 02:53:39 CDT
