How many rows...?

I'm developing an app that will allow a user to track clicks and sales by date/time. However, I was wondering with the potential for a TON of clicks, is it feasable to track individual clicks in a SQL Server 2000 or 2005 database? I'm talking potentially 50,000 products receiving thousands of clicks per day, coud the db handle that kind of traffic? Or should I stick with a running total of clicks per product, and forget about the ability to see a breakdown of clicks per day, etc?That data is going to get out of control rather fast. However you can keep a running total by day.|||How many rows can a typical table handle? 1 million? 500 million? 1 billion? More? That will help me figure out if I can track clicks daily, or if I have to track weekly or monthly.|||The only limitation of rows per table in SQL is the storage available, see 'Maximum Capacity Specifications' topic in SQL Books Online