I quit a gig within the last year where the company was on DB2 (8) and the data was scattered. Their daily processes were pushing 22 hours to complete, and their chosen solution was just to delete historical data, so that they couldn't even tell their customers what happened the previous month. Of course, the same team had been building their PL/I code since the 1980s, so there was no way to get them unstuck without some executive decisiveness, and that wasn't happening. They wanted a data warehouse for business intelligence in their oracle system. I signed a contract for golden gate with implementation and then walked. Really, the place was a mess. WebFocus for reporting, an excel reporting team because they couldn't get data from WebFocus, a java team where the last 2 architects had quit within a year, a stealth jasper reports team that had been working on the same goal for years with no deliverable, etc. Really, the only thing in the entire place that worked at all was the DB2, and on that alone they were making money hand over fist. It was an amazing scene.

Thanks. That is a new one to me.

From what I have read, the indexing tools in MongoDB are superior to CouchBase. Can someone confirm this?

Thanks. We are not trying to make this deliberately difficult. If we go with NoSQL, it seems MongoDB is the one people are leaning towards.

We are looking at 99% incoming data, 10-12 fields, 1000-2000 per session per week, X as many users as we can get.

Thanks. This is how we were going, but as we have a blank canvas at the moment, this was a why not sort of decision to look at NoSQL solutions.

We don't know how big to scale. A few thousand users, a few million?? Apps in the wild are like this sometimes. New to NoSQL and really just wanted a good place to start with a platform that would let us scale. I don't want the Oracle on million dollar hardware problem again.

Not bait, simply dipping my tow into the NoSQL waters. I have been a developer for almost 20 years now and can spin this up with a SQL database in under an hour. The big thing here is that it be highly scalable (thus the iphone/andriod - you never know how big these will get, or how fast) and we are able to get some kind of structured time based reports out on the back end.

Yes!! How will the man do his job is the only thing that counts. I would hate for my personal activities to be brought into work, which is why I keep them private