Hi there,I'm tracking views of online articles. In the db table, there's one row per article per day. So in other words, a record is being kept of how many hits each article gets per day. The website then shows a 'most read' list for the week and the current day.After a few weeks I've already got 70000+ rows so I expect that after a year there'll be a million or more rows.Is this going to be an excessive burden for the db? If so, is there anyway I can archive the info without losing any resolution to the reports that can be generated from the data?Here's the table schema..CREATE TABLE [dbo].[tbl_newsarticle_count]( [nID] [int] NOT NULL, [Date] [datetime] NOT NULL, [Count] [int] NOT NULL, CONSTRAINT [PK_tbl_newsarticle_count] PRIMARY KEY CLUSTERED ( [nID] ASC, [Date] ASC) ON [PRIMARY]) ON [PRIMARY]GOUSE [newbury]GOALTER TABLE [dbo].[tbl_newsarticle_count] WITH CHECK ADD CONSTRAINT [FK_tbl_newsarticle_count_tbl_newsarticle] FOREIGN KEY([nID])REFERENCES [dbo].[tbl_newsarticle] ([nID])
Cheers, XF.
What do I do with all this data?
Posted - 2008-03-09 : 18:48:56
