Mladen Gogala <mgogala_at_adelphia.net> wrote in message news:<pan.2003.12.06.21.24.37.509835_at_adelphia.net>...
> On Fri, 05 Dec 2003 07:06:26 -0800, Ryan Gaffuri wrote:
>
> > We are using an NAS. Are there any conventions to handling Physical
> > I/O distribution on NAS or SANs? They are relatively new. Since we
> > dont control which disk or mount point datafiles go on, we really
> > can't spread out the I/O. Does it matter if we put tables in different
> > datafiles then?
> >
> > any conventions or articles would be helpful.
>
> http://www.baarf.com has some very good articles. In addition to that,
> you want to keep things separated for administration reasons, too. It's
> much easier when large tables are in one tablespace (uniform extent size,
> 256m/extent or 512M/extent), smaller ones separated elsewhere
> (autoallocate space) and medium sized tables in their own tablespace
> (uniform extents, 64M/extent). Also, indexes should be held separately,
> as well as the structures for tools (Developer & Designer) and
> applications.
> You also want to have several control files, just in case, and several
> (rather large) redo logs.
seems like james morle has the only SAN or NAS oracle article out
there. hopefully there will be more in time.
Received on Mon Dec 08 2003 - 13:30:18 CST
