: RE: When should a table be
partitioned?
[EMAIL PROTECTED]
Cheri,
Just wondered even when you have a table with data still you can partition
it or you have to create a new table with partitioning and load the data
from old to new one. Is it right or not?
-Original Message-
Sent: Tuesday, January 22, 2002 8:10 AM
To: Multiple recipients of list OR
Cherie,
We used the data volume and performance criterion while deciding to
partition our tables. One of the major tables had grown over 100Mil rows and
had 4 indexes. All tables had 4 digit YEAR field and most queries used YEAR
in them, so it was a no-brainer. A few important queries were modifi
Cherie,
I use the row count ,table size, and comonality method to determine
which tables to partition. The majority of our data is DATE driven both
in the record and the query so I partition the tables by date range
using the date range most commonly queried. The limits of the OS and
datafile siz
: rootcc:
Subject: When should a table be
partitioned?
01/18/2002
Cherie - I am relatively new to partitioned tables, but I have two criteria.
1. Partition the table for performance. If you have some significant queries
that will be doing full table scans (not unusual for data warehouses), then
may partition so the full table scans just scan a selected partitio
We have a number of partitioned tables in a couple of existing data
warehouses.
We are working on the design for a new warehouse and need to decide which
tables should be partitioned.
For you folks that have partitioned tables, how do you decide which tables
to
be partition? Some tables with v
