Re: database sizing estimates using partitioned indexe
- From: "Bradd Piontek" <piontekdd@xxxxxxxxx>
- To: oracledbaquestions@xxxxxxxxx
- Date: Tue, 30 Sep 2008 13:20:06 -0500
I"m a little confused as to what your question is.
Isn't it enough to use USER_SEGMENTS based on segment_name and
partition_name??
Bradd Piontek
"Next to doing a good job yourself,
the greatest joy is in having someone
else do a first-class job under your
direction."
-- William Feather
On Tue, Sep 30, 2008 at 1:09 PM, Dba DBA <oracledbaquestions@xxxxxxxxx>wrote:
> 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 ?
>
- Follow-Ups:
- Grid Control on SLES10
- From: Stuart Blackburn
- 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
- Grid Control on SLES10
- From: Stuart Blackburn
- database sizing estimates using partitioned indexe
- From: Dba DBA