Re: Newbie: Number of tables (fine grained vs. coarse)?

The application type, OTLP or Warehouse, and the application should be the driving force here. The million+ rows of data is irrelevant without the context of the application(s) that will be using the data. Physical table structures for the two types of applications look much differenct. OLTP applications tend to handle more tables and relationships better than a Data Warehouse would. Working in these two braod areanas with you still have to know the data and how it wll be accessed to get the optimal physical table design.

les_hartzman_at_yahoo.com wrote:

> I'm by no means an expert on databases and have only had some basic
> coursework on them, so all help, especially in the case of Oracle, will
> be greatly appreciated.
>
> I'm coming up with an object model to represent the data that could be
> in a database, and right now there appears that if we created a schema
> (relational) based on the number of objects we have (even using
> inheritance) would be large (a relative term - no pun intended). The
> number of records could exceed 1 million.
>
> The number of tables to represent the objects could be 30. I would
> think that the access to this data would be faster as the individual
> tables would be smaller than a few large ones, even taking joins into
> account. This approach as opposed to checking through a subtype column
> for type determination.
>
> Can anyone pass along any of their experiences with this type of
> situation?
>
> BTW, we're probably looking at Oracle 8/8i for this.
>
> Thanks in advance.
>
> Les
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Sat Apr 22 2000 - 00:00:00 CDT