Comment Re:Use databases! (Score 1) 235
I'm amused by all the
one SQL database? As in, one ginamic SQL database? yeah, that's a headache.
OTOH, one SQL database per "type" of data (i.e., "last summer's research.sql")? Hell yes. If it's not in a database, you need to spend the ten minutes to learn how to make one. MS Access exists for a reason, and this is it. It won't be a very pretty db, but it doesn't need to be -- it'll be indexed, searchable, and more or less protected.
The only reason NOT to put it into a relational database is if you have some system that's essentially a database already, and in that case you can just leave it as-is. (Microsoft's SharePoint, if the data's small and simple enough, is an example.)