× 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.


  1.  Home
  2. MIDRANGE-L
  3. May 2011

Re: DataArea vs. Tables

DrFranken wrote:
If you write to a *DTAARA the system forces the write to disk. Now if
you have write cache on your disk controllers the write to that
cache is considered 'well enough' and processing continues. However
if you have no cache (as a low end system with mirrored disk might
have) then the write must be actually to disk.

My perspective on using data areas is that they should be read mostly / update rarely.

This is key to the idea of using them for configuration options that don't get updated often.

if you are updating the *DTAARA with (say) current record position in
a massive table (for crash recovery for example) then EVERY record
position gets forced to disk and that slows the job *DRAMTICALLY.

Wouldn't journaling be more appropriate for that kind of functionality anyway?

david



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.