Us too... But we store the tools in a "freakin database" because that CAM thing stores it in a bunch of own structured text files that change with every damn version they release. We've built our own Tool Management Software, because the API doesn't change as often as that proprietary kind of "database" (as they call it), and inject the tools via that API.
Makes updating the customer's "database" a lot easier, just adjust the dlls to those with the new API - done! Same dlls for every updating client instead of lots of files for every single customer. Cost them several days of (our pretty expensive) work days previously. Now they buy our software once
Depends on the use case. I think most projects using NoSQL are only doing so because it's another buzzword.
In most cases a relational database is the one you want and forcing it into NoSQL just risks data integrity and makes everything slow.
My point was more that these NoSQL databases have been used in loads of places they shouldn't have.
Hopefully your project isn't one of those. I've not worked on a project with a valid use case for it though I would like to at some point.