1 table for many records or many tables with few records 
Author Message
 1 table for many records or many tables with few records

Hi,

My friend is programming an web application to record employes registration
to social events and she wants to create a new registration table each time
a new event is scheduled.  Each distinct table will hold registration
information for specific event and, at some expiry , the table will get
dropped.

From my point of view, it would be better to hold registration information
for all events in one single table and delete records instead of tables when
comes the expiry date.

My question are:
1) Is there a problem to generate and drop table just as often as we would
add and delete records in one table?
2) How many records can we add to a table before we see performance
degradation in simple queries?

Thanks,

- Sylvain

Can anyone tell me what is the best practice in the following.



Tue, 13 Sep 2005 18:18:27 GMT
 1 table for many records or many tables with few records

It sounds like there should be three tables needed...

Employee
Event
EmployeeEvent (this is a many-to-many between the other 2)

Having one Event table with rows for each event is better
then separate tables..  

The performance question you asked depends on some things
like are you running this on her laptop? or a real
server?  How many parties could one place have anyways?  
(and are we all invited to the next one??)  In a thin many-
to-many table (mostly integer columns there), you could
store millions of rows probably and as long as they're
indexed be ok with performance...  but again, it depends
on hardware, other processes on the same box, etc...  Bruce

Quote:
>-----Original Message-----
>Hi,

>My friend is programming an web application to record

employes registration
Quote:
>to social events and she wants to create a new

registration table each time
Quote:
>a new event is scheduled.  Each distinct table will hold
registration
>information for specific event and, at some expiry , the
table will get
>dropped.

>From my point of view, it would be better to hold

registration information
Quote:
>for all events in one single table and delete records

instead of tables when
Quote:
>comes the expiry date.

>My question are:
>1) Is there a problem to generate and drop table just as
often as we would
>add and delete records in one table?
>2) How many records can we add to a table before we see
performance
>degradation in simple queries?

>Thanks,

>- Sylvain

>Can anyone tell me what is the best practice in the
following.

>.



Tue, 13 Sep 2005 19:21:06 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. Cannot add record to Visual Foxpro table after deleting all records in table

2. one table with lots of records or more table with less records

3. Fetch record into a plsql table (record.column_1 into table(index_1))

4. Getting a few records from tables

5. Lots records not being posted in table, identity_column shows missing records

6. creating a table of pairs of record IDs for records with similar content in text field

7. Counting Records in Table not Connected to Records in Another (SQL Newbie)

8. Update record with data from another record in the same table

9. Update record with data from another record in the same table

10. SQL7 server crawls (locks) when deleting records from a 3 million record table

11. Joining tables / using another record's value if record doesn't exist

12. How can I get records WITHOUT relating records in another table


 
Powered by phpBB® Forum Software