I'm currently in the process of evaluating the design, and possible reimplementation of an in-house app our engineers use.
Although the application handles large amounts of data. Only two sets of values (floats) are saved along with a simple name and description of the data. In my opinion the current application is in overkill territory using a normalized access database to store what evaluates to 7 fields of strings and floats.
At what point do you start looking at transitioning from a flat file or serialized XML to a relational database or vice versa?
I would recommend using a lightweight database like SQLite which reduces a lot of the overhead of using a database.
http://sqlite.org
Databases can have huge advantages over flat files, even if you only have a single table with a few values.
They can dramatically improve query speed if you have a large amount of data - if you only need to find one value via a key, pulling this from a DB with an index prevents you from having to parse the entire file and search.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With