ShawnMolloy
MIS
Hi Experts!
While creating a table in a production SQL 2005 database to hold the "views" of a user profiles, I realized that this table will very quickly grow to such a scale that worries me a bit. I don't have exp w/database of this volume. Can anyone who is more weathered in the database world tell me of any cavets of such a table?
Here is the table schema:
UserID INT
ipAddress CHAR(50)
dateAdded DATETIME
This site has millions of users, each user can have potentially hundreds of thousands of views. (think myspace)
Thank you,
Shawn Molloy
Seattle, WA
While creating a table in a production SQL 2005 database to hold the "views" of a user profiles, I realized that this table will very quickly grow to such a scale that worries me a bit. I don't have exp w/database of this volume. Can anyone who is more weathered in the database world tell me of any cavets of such a table?
Here is the table schema:
UserID INT
ipAddress CHAR(50)
dateAdded DATETIME
This site has millions of users, each user can have potentially hundreds of thousands of views. (think myspace)
Thank you,
Shawn Molloy
Seattle, WA