definitely incremental - especially if the events that cause you to update your data take place incrementally. Doing the update as events arrive distributes the processing workload over time, and makes you design a system that has some robustness.

Think about what those evenst are, how they are signalled to your system, and what the change on your data is for different events. Work this out with pencil and paper as far as you can. Work out what it is you don't know (not so much about the technical side, more about the proper behaviour of the system).

What inconsistent states can arise as a result of unexpected events? How will you hanlde them?

What are the invariants of the state of your system?

Design database queries that update you db for expected events. If updates affect several tables (ie to preserve the links between tables that you mention, which by the way are a GOOD thing generally), find out how to lock tables so that the data accessed by users will always be consistent.

DO take the time to make sure that your database design is good, and correctly normalised. Not doing this will cost you many many hours down the line. If you don't know what this means, check out some of the many tutorials on teh web

In reply to Re: RDB updates: rebuild from scratch vs. incremental by danmcb
in thread RDB updates: rebuild from scratch vs. incremental by tlm

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.