Re: Table growth - disk sizing

Thanks Jared. 
It is clearer now what they want - to avoid disk hot spots ( group
tables by read/write and growth characteristics to avoid hot spots on
disk. Disks are SAN,  RAID 0+1 - so there is no precise control over
file location on disk. Why separate objects into tablespaces/datafiles
when you don't know where read/write is going to end up anyway ?

Ranko.
  




On 8/22/05, Jared Still <jkstill@xxxxxxxxx> wrote:
> I use dba_space to gather space stats on objects, once per week.
> 
> Not exact, but has served well enough the past few years to 
> give a reasonable estimate of growth rates.
> 
> Jared
> 
> 
> 
> On 8/22/05, Ranko Mosic <ranko.mosic@xxxxxxxxx> wrote:
> > 
> > Hi all,
> > I need to estimate table growth. Any ideas except standard select
> > segment_name, sum(bytes)
> > from dba_segments
> > group by segment_name;
> > and likes, done every day to extrapolate growth ?
> > 
> > Any experiences with alter table table_name monitoring; etc. 
> > 
> > Regards, Ranko.
> > --
> > http://www.freelists.org/webpage/oracle-l
> > 
> 
> 
> 
> -- 
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist 
> 
>
--
http://www.freelists.org/webpage/oracle-l

Other related posts: