A single table with a column for "user" is much better. Put an index on the "user"
column to speed it up.
If you created new tables for each user you would have to alter your database (create
table and drop table) for every new user and deleted user. You would have to come up
with a naming scheme for all these tables so there are no name collisions.
At 09:53 AM 11/6/00 -0500, ibtoad wrote:
>I am setting up a website in which people are creating records and storing
>them in a database (Access 2000 at this time). Am I better off with a
>single table that includes all of the records of all users or should I set
>up a seperate table for each user? I am pretty sure that the seperate
>tables would have better performance but will probably be harder to upgrade
>to SQL 7 later. Please let me know your opinions.
>
>
>Thanks,
>Rich
>
>------------------------------------------------------------------------------------------------
>Archives: http://www.mail-archive.com/[email protected]/
>Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
>with 'unsubscribe' in the body to [EMAIL PROTECTED]
---------------------------------------------------------------------------
Peter Theobald, Chief Technology Officer
LiquidStreaming http://www.liquidstreaming.com
[EMAIL PROTECTED]
Phone 1.212.545.1232 x204 Fax 1.212.545.0938
To put this contact information into your Palm device, click here:
http://www.coola.com/cgi-bin/addinfo.cgi?pid=15803&rid=972879910&type=A
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
