Re: Big Tables? Real Life Examples.....

bchorng_at_yahoo.com wrote:
<snipped>
> You can use partitions too. It will cut down your index depth and
> reduce query cost.

Beg to differ. Largish tables? You *MUST* use partitions.

Not partitioning "large" tables is performance suicide as it leaves you without any room for scalability and without proper data management.

"Large" is of course in the eyes of the beholder. I have partitioned tables that only contains 1000's of rows - as part of a VPDB. Allows me to treat each virtual private table as a physical entity via its associated partition. I have partitioning on very dynamic tables (millions of transactions per day), with partitioning providing a hourly sliding window. I have partitioned tables on very large tables.

Without partitioning.. I would have had serious problems all around in managing the data volumes and providing scalability and performance I have.

IMO partitioning plays such a major role, that every table that you design for a physical db implementation, must be considered for partitioning too as part of the indexing and data management requirements of that table.

--
Billy