This system is for "members/users" of our webapp. What if, for each user that used this service (its and add-on), we created a new table on the fly. That way each table would be used for that users tracking only and not for all the users. Is that a viable idea?
BrookD At 03:41 PM 6/13/2006, you wrote: > >If you do not need to keep track of IP addresses and dates, I would go this > >route. If not, then make sure you have your columns as small as possible > >and maybe purge the info on a regular basis. > >If you do need that info you do best to have a table like Jabob proposes >anyway. Any inserts into a table you yourself proposed doesn't really do >any harm to processing. If you need to do a query that counts the number >of hits on that table, that will probably slow down as the table grows. So >you can do the count (to determine what to show) on 'Jacobs' table' and >have the other info in a separate table. OR just analyze your webserver >logfiles for that info later on :-) > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:243417 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
