Greg,
We have been developing with SynergyDE for almost 30 years (Synergex) and they have an extremely good ISAM file system with ODBC for access externally via SQL statements. They have just recently released their ISAM file system as a NOSQL offering which may meet your criteria. www.synergex.com [image: cid:[email protected]] *Regards,* *Steven Parish*** *Software Architect | BusinessCraft Pty Ltd | www.businesscraft.com* Tel: (02) 4965 5555 | Mob: 0417 688 599 | Fax: (02) 4965 5333 | Level 1, 270 Turton Road, New Lambton, NSW 2305 ------------------------------ *Disclaimer* The information contained in this and associated e-mails and any attachments are confidential and were only intended solely for the use of the addressee. If you have received this e-mail in error, please notify the identified sender by return e-mail and then delete all copies of this and associated emails and their attachments from your computer and or your computers system. Opinions, conclusions and other information in this message that do not relate to the business of BusinessCraft Pty Ltd shall be understood as neither given nor endorsed by it. It is your responsibility to check the message and any attachments for any viruses before use. BusinessCraft does not accept liability for any loss or damage that may result, directly or indirectly from your receipt of this message or any attachments contained within it. *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Greg Keogh *Sent:* Tuesday, 4 June 2013 12:25 PM *To:* ozDotNet *Subject:* Lightweight database Folks, an app has just grown with a new feature that needs to store of "users", "jobs" and "reports" and the joins between them, If I was using SQLite it would be 3 tables with joins. However, rather than use SQLite this time I'd like to consider an alternative that's even more lightweight to setup and use. The app does not currently use any database technology and the guys managing the project are actually scared of them. Can anyone recommend an in-process database (not necessarily relational!) that is has a friendly managed API, small footprint, not too complicated and is easy to get going? I know this is a lot to ask, but there may be some NoSQL options around that I'm not aware of. The most important issues for me are: (1) *Minimal dependencies* (2) *Simple managed API*. I'm running a few web searches now for such things, and I can see Redis, Mongo, Couch, Raven, db4o, Cassandra, Eloquera, Lucene, and the list goes on and on. There are too many choices and it would take many days of hard slog to work out which one would be suitable. So perhaps someone has already been through this process?! I've been tempted many times over the last 10 years to write a pure managed single-file database with indexes, and nothing much else (no transactions, no client-server, no schemas, etc). However, I decided to leave it to the experts, and it looks like there are too many of them, and they all over-engineer their works. Cheers, Greg K
<<image001.png>>
