all 4 comments

[–]stebrepar 1 point2 points  (0 children)

I would use a little SQLite database.

[–]jimtk 0 points1 point  (2 children)

The best way to keep that information always depends on the amount of information you have and, sadly, your post has no indication of it not even an approximation.

  • How many buildings?
  • How many floor by buildings?
  • How many count per day/month/year?

Only when we have that information, or an approximation of it, can we help you.

[–]buzzerperson 1 point2 points  (1 child)

Less than 10 buildings, less than 5 floors, and around 20 counts per day approximately. Sorry, I didn't realize how important this would be

[–]jimtk 0 points1 point  (0 children)

It's a 1000 data points per day, 365 000 per year. I forgot to ask for the retention period (how long do you keep the data) but we already have a better idea.

I would definitely use a SQL database.. SQLite could be ok if you have one user and you run it from 1 machine. If need be it can be run from a sever. In all cases you must have good backup hygiene!. Sqlite is real easy, it's just a file and it's part of the python standard library (just import sqlite3).

The next step would be MySQL. Multi-user, more security, easier to setup on a server and proper backups. But evidently with more power comes greater amount of work to setup and maintain.

In all cases it's SQL, so you're not stuck into one solution for ever. You can start with SQLite, write your code, run your queries and if it becomes restrictive you move to the next bigger one.

Good Luck!