Results 1 to 5 of 5
  1. #1
    Join Date
    Jul 2003
    Posts
    4

    alot of small tables, or 1 big table?

    as far as processing requirements, is it generally better to have alot of smaller tables that you link through joins, etc, or to have 1 big table?

  2. #2
    Join Date
    Sep 2002
    Location
    UK
    Posts
    5,171

    Re: alot of small tables, or 1 big table?

    It is generally better to have the right number of tables to normalise your data - no more and no less.

  3. #3
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    What kind of processing requirements? What layout of data? How frequent are the updates?

    This is a juggling act, trying to decide what resources you want to conserve, what resources you can be fairly generous with, and which issues are important to "hold the line" on just to preserve what little sanity you might have left!

    -PatP

  4. #4
    Join Date
    Jul 2003
    Posts
    4
    im not quite sure of that yet, as i am still in the planning process. i was looking for a 'rule of thumb' kind of answer, something that in most normal casese should be followed.

  5. #5
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Then I'd suggest that you take the data to at least third normal form. That will avoid most of the ugly problems that you can find with INSERT/DELETE anomolies, but still keep the tables from being fragmented to oblivion.

    -PatP

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •