Optimal design for database scenario : <p>I am building a system that keeps track of the visits of members to some clubs.</p>

<p>As I see it, I have 2 options to keep track of the visits, just insert one row into the visits table for each visit and when I need the total, I can just select count, when I need to display i can just do a simple select.</p>

<p>The problem, this is going to grow fast and I am sure I will have eventually like millions of rows just in this table.</p>

<p>Can mysql handle this with ease? Or better implement the second option, one row for each member, and store in one of the row cells the total amount of visits and in another cell the last 60 visits (not really more needed).</p>

<p>I guess the answer as to what's better is obvious but I am curious about how much mysql can handle because the previous system implemented 1 row for each visit.</p>
