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

RE: Line Item Budgeting

Forget multi-member, it's not worth it.

SQL performance would be enhanced by dividing the table into members.


Why? SQL has no problem with many rows, why would you believe that SQL
would be faster. OK, I guess in _theory_ there are fewer rows, therefore
fewer reads, therefore faster, but in reality you can't tell the
difference.

Back-up and restore procedures would run quicker by simply backing up
the *last member.

Really. Seems to me simplicity is the king of backup/recovery. I can see
them constantly backing up *last, and then needing to restore the entire
table after a crash and saying "tapes from last year, nope... can't we
just use last nights."

Actually I'd think your programming would be simpler too as you could
simply have a key for the year and then SETLL or SELECT as needed.

The copy last year to this year is a trivial program, using that as a
reason to go multi-member is not a valid argument.

-Walden


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.