Database Table Design/Layout for Analytics type data?
I am looking to store views and clicks, with the possibility of other types of data moving into the future.
I understand a rough idea, but can't quiet comprehend the best way to layout this data. There are lots of ways to do it, but whats the right way?
Googling hasn't helped me find much of any use.
I could:
- Create a column labelled 1-365, then store the data for that day, keep a year per user
While this makes sense in my head, and would work, this doesn't scale long term if I want more than one year of data, and would also take a lot of space on day 1 of a new user with 364 0's for the sake of it.
I would also need to store a start date, then calculate any functions from that start date, also seems off.
I'm not asking for a 'explain everything' answer, but guidance to internet resources where I could learn how this SHOULD be done, rather then whatever works.
Thanks!
I understand a rough idea, but can't quiet comprehend the best way to layout this data. There are lots of ways to do it, but whats the right way?
Googling hasn't helped me find much of any use.
I could:
- Create a column labelled 1-365, then store the data for that day, keep a year per user
While this makes sense in my head, and would work, this doesn't scale long term if I want more than one year of data, and would also take a lot of space on day 1 of a new user with 364 0's for the sake of it.
I would also need to store a start date, then calculate any functions from that start date, also seems off.
I'm not asking for a 'explain everything' answer, but guidance to internet resources where I could learn how this SHOULD be done, rather then whatever works.
Thanks!
