×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Went to an IBM & Partner intro to 8.5 last week. One of the new options
we may look at requires transaction logging be fired up. Most of the time
when I hear about transaction logging it makes me think of something
primarily run in a lab or on a test machine. Because, they mention
keeping your data on one drive and your transaction logs on another drive.
Well, my machine has ninety disk drives. All Raid 5 protected. Does it
really make sense to put the transaction log on dedicated disk? On the i
that would involve Auxiliary Storage Pools or ASPs. In theory I could
have two ASPs: Main data in one and transaction logging in the other. I
can't imagine it would take more than a few 70gb disks to do transaction
logging.
Raid sets smaller than 4 drives are known to have serious performance
implications. Technically you can do a 3 drive raid set, but unless the
customer is just migrating from a S/36 they will notice the performance
hit versus a 4 drive (or more) set.
Is this separate disk stuff recommended on a "real" os?
Do I need a full RAID set in an ASP?
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
