1: The logs are selected quite often based on indexed columns, and this is done via a web portal graphing tool. Maybe I shouldn't refer to them as logs for clarity, but the data is specific snmp fields where a schema fits well and the queries are fairly basic with some group by aggregation.
2. I see. I was thinking of using myisam to store the "log" tables which makes dropping a table equivalent to deleting a file. 3. Anytime I wanted to delete a device, the operation took some time, and that table is read/write intensive so I am afraid that deleting 5M records would interrupt things. (using innodb) 4. I am not expecting more than 5k customers. But I can imagine how managing that can be a hassle. Should I keep things the way it is, single database, single table for all device logs of all customers? Or there is a better approach I can take? Thanks -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To view this discussion on the web visit https://groups.google.com/d/msg/sqlalchemy/-/yviCZpEc-fwJ. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
