Wednesday, 15 February 2012

sql - Database Design Issue due to Volume -


I actually have a generic database query. I have created a table in my database that tracks clicks on my website. The table structure is as follows:

  • (PK) - ID,
  • (FK) - PageID,
  • (FK) - Contact ID, < / Li>
  • Date is

    The problem is that with large user sets, and large amounts of clicks through data, the number of rows in this table is 20- 30 Ilian Range Can I settle for a different way that I score reporting on this data? PAGIDID = P. PAGID C CDTTE = 5/1 / 2013 and CDDT & lt; 6/1/2013 and C.PAGEID = XYZ

    This requirement is well Take care.

No comments:

Post a Comment