Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Dear All, i'm developing a web application with a lot of event to track in it. I'll install the application in ca. 10 web server and I need to have the tracking event saved in a db in order to be analyzed.

I'll receive 100K events/minutes = 144 millions events a day an event row is (event type, user id, object id, context id, session id, timestamp)

I think about store them in a MyISAM table and then, every day, change the table name according to the date (i.e. log20090826, log20080827 and so on). Have you other/best ideas? I can use, if more performant, other RDBMS.

another question: is there any method to know the timestamp of a row without having it explicitly written (no space used)?

thanks, Andrea

share|improve this question

For such a big volume of data I would recommend you to use text log files and to parse them. In 6 months you'll have 26,000 millions records and I'm sure you'll not be able to analyze them using SQL.

Also if this is important you could try to log the data in BigTable or Hadoop. These not-SQL databases will do the job quite well due to your data model.

Here is an article that you help you.

share|improve this answer
thanks. I never installed Hadoop: is it simple? can it cooperate with .NET applications? which type of hardware is needed? – andrea Aug 28 '09 at 21:59

MyISAM is OK, just make sure you use the "INSERT DELAYED" prepared query, so the server relaxes a bit :)

share|improve this answer
thanks for your answer. what about the possibility to not insert the time stamp? Andrea – andrea Aug 27 '09 at 13:32
TIMESTAMP field type is auto-filled with a right timestamp when you insert NULL in it :) see the manual, that's handy – kolypto Aug 28 '09 at 18:30
A row MUST contain a timestamp, else there's no way to know it. If you don't need an exact timestamp - you may approximate it: if you have 1000 log entries for one day, then the first record is somewhere near 00:00 and the last is 23:59. Others are in the middle, linearly. No other methods to save space, sorry :) You can use compressed tables to save space, but this will slow down operations on that table. – kolypto Aug 28 '09 at 18:33
thanks. I think I should try some approximation technique. Andrea – andrea Aug 28 '09 at 19:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.