While I appreciate everyone's input on optimal hardware configurations, I
can't really change the hardware that will be used. It's already out of
the box and running in the computer room. I would be interested in
everyone's opinion on the best way to lay out dbspaces given this hardware
configuration, though. BTW, I think I misinformed you about some of the
database sizes -- the largest database that will be running on this box is
under 5 gig.
Regards,
Vickey Crouch
Vickey Crouch wrote:
> Hello, everyone,
>
> Would anyone out there like to share their thoughts on the best way to
> lay out dbspaces? We have several databases, ranging from 50 mg to
> 200 gig in size, that we're migrating to a new platform. Our new
> platform is a Sun E4500 with 8-400hz processors and 1.5 gig of RAM. We
> have an A-1000 disk array with 18 gig drives (10,000 r.p.m.), and a
> single controller. The storage array is set up with a hardware level
> RAID-5 configuration. We're using Veritas to manage storage. The new
> platform will be running IDS 9.2 with Solaris 2.7.
>
> We're trying to decide how many dbspaces we should allocate. Should we
> allocate at least one dbspace for each database, regardless of the
> size? Should we allocate one dbspace to dump all of the little
> databases into? Should we allocate multiple dbspaces for the large
> databases? Are there any advantages to fragmenting dbspaces with a
> RAID-5 configuration? Any suggestions for a good chunk naming
> convention?
>
> I'm very interested to hear your thoughts on this subject.
>
> Regards,
> Vickey Crouch