modify in memory and delay writes to disk and you can kiss it goodbye on poweroutage/system crash.
I took an exception on transaction support. He didn't specify
what kind of database he needs - if it's being modified
heavily, you want to have something that makes sure no data
gets lost on a crash. But if all he does is querying, having
it all in memory is what you want.
Abigail
| [reply] |
This is not going to be heavily modified by any means. Adding records will occur at a specific time each day. From that point on it is mostly a query and calculations of the data gathered, and then throwing results into an output file that will be read by a person.
It is the calculations that I will do that worry me about memory.
| [reply] |