RE: database sizing estimates using partitioned indexe
- From: "Michael McMullen" <ganstadba@xxxxxxxxxxx>
- To: <oracledbaquestions@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 30 Sep 2008 14:37:04 -0400
I think user_segments would do the job nicely. What's wrong with using
segment_name along with partition_name?
_____
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Dba DBA
Sent: Tuesday, September 30, 2008 2:10 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: database sizing estimates using partitioned indexe
We partitions by day and by month depending on the table. All of our
partitions have names of the form
PART_YYYYMMDD or PART_YYYYMM
I am trying to calculate sizing estimates/day and by month (so they can stay
ahead of adding storage).
since all my partitions have the same name, user_segments is not useful.
for data I was using using_tab_partitions and taking blocks*blocksize to get
the size/day.
I see "leaf blocks" in user ind_partitions. Not sure if that is enough
blocks to get a good estimate per day. Note that 1 partition is one day or 1
month.
any suggestions ?
- References:
- database sizing estimates using partitioned indexe
- From: Dba DBA
Other related posts:
- » database sizing estimates using partitioned indexe
- » Re: database sizing estimates using partitioned indexe
- » RE: database sizing estimates using partitioned indexe
- database sizing estimates using partitioned indexe
- From: Dba DBA