Re: Partitioned table or several smaller tables?

John wrote:

> Yes, we do have the patitioning option. So it is not a concern here.

One problem solved.

> The question is whether we should put rarely accessed data together
> with active data all in one single table.

Absolutely and without a question. And if any of it is unmodifiable make the tablespaces in which it is stored READONLY.

  We will always query one
> partiton, in the case of partitioned table, or one table, in the case
> of several indivisual tables, at a time. Data volume is fairly big.

Then leverage the money you spent.

> Would putting all the data into one single table degrade query
> performance?

No. That's the entire point of partitioning.

  Any other issues that might impact us negatively, if we
> go with partitioned table?

Not that I can think of. On the positive side your management might decide not to terminate the lot of you for not using such an expensive and valuable resource. ;-)

>
> John

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)