Results 1 to 2 of 2
  1. #1
    Join Date
    Mar 2006

    Question one large table or many small subtables? (was "any ideas?")

    Am designing a database for an online dating application.A user is supposed to register and thereafter create a profile.The profile contain a user background,basic,appearance and interests information.Should i have one large table in my database to store a user profile or should i partition the table into small subtables e.g i divide the table into subcategories(basic,appearance,background,interest s).
    Last edited by anthmaina; 03-30-06 at 04:46.

  2. #2
    Join Date
    Sep 2002
    Logically, you want one table for all attributes that have a 1:1 correspondence with the user, and other tables for attributes that have a many:1 correspondence - i.e. a normalised set of tables for the data.

    Physically, if you have very many (hundreds or thousands) of 1:1 attributes then your DBMS may require or prefer that you vertically partition into a number of smaller tables.

Posting Permissions

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