Hi there, I am in process of designing my db schema for a web service that monitors servers on an intranet and has to store a lot of fields like cpu, mem, load avg, swap, and plenty more for a period of time. The fields might change in the future.
Any recommendations on how to design a schema that will accommodate for that? I would like to stay away from schema-less DBs for various reasons but I want to make sure an RDBMS is the right choice too. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
