Posted by Martin on 12/08/05 23:08

> Everything is relative. For a small database, < 50 MB, it may be possible
> to encrypt it entirely and only hold the decrypted version in main
> memory. Then again, memory can be dumped.

I've experimented with a small database flat-file database (non SQL, non
Access) and in-memory tables. The process is horribly honerous. In memory
tables, at least what I've been able to get to using something like VB6, are
not really setup to be full blown databases but rather a place to hold
temporary data it seems. As such, there doesn't seem to be a way to load a
small database (consisting of a number of tables) into memory and have it
act as a database.

What occured to me is that, perhaps, one can create a RAM-disk on the fly,
tell it to be encrypted and move/copy the DB into it on application start.
Then the OS would take care of the matter? On application termination the
RAM disk would be destroyed.

My application would more than likely be single user. It made me wonder how
high-security DB's are handled. It seems to me that data is, for the most
part, fully exposed.

-Martin

[Back to original message]