RE: neebee: on table designs.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



small tables are easier to maintain and grow and quicker to search. need more info about the data to really help. probably 1 main clients table with basic info and then 1 or more smaller tables that hold certain specifics

bastien

From: "phpnews" <tony.yau@xxxxxxxxxxxx>
To: php-db@xxxxxxxxxxxxx
Subject:  neebee: on table designs.
Date: Wed, 17 Nov 2004 07:05:27 -0000

Hi All,

    I have 5000+ individual clients, each clients may have 100+ records.
Each client can modify to their own records.

    In the order of maintenance, robustness, scalability then performance,
which of the following do you think is best.

    i)    1 big table with 500000+ records
    ii)    5000+ small tables with 100+ records (1 table for each client)?

    At first I thought (i) but then for robustness a colleague pointed out
that on (ii) if clients screw up their own table it will not affect anyone
else!

any comments/suggestions are very much appreciated
tony

--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


-- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [PHP Users]     [Postgresql Discussion]     [Kernel Newbies]     [Postgresql]     [Yosemite News]

  Powered by Linux