Link Details

Just had to because he used OLTP. It is a term for the days when you do "Online" transactions (Green Screen) and "Offline" transactions (Batch). It was not about the database. It was about the overall system. You would use the same database either for online or offline. This databases were mostly Hierarchical like IMS.

What is the best term? I call it an Operation Datastore. Maybe there is something better. But OLTP is not it.

"OLAP has not such requirement. Nobody needs instant information to make strategic business decision. " Is he sure? Maybe not strategic, but important decision might need to be "instantly" made.

mknutty Thanks for the comment and the opportunity to make clear some possibly confusing point. Please understand OLTP and OLAP terms in the "classic" acronym-antonyms sense (see Wikipedia and most Data Warehouse texts). That definition perfectly matches your comment: operation datastores updates are transaction-level isolated (no matter if you use IMS, SQL or graph/object database) while OLAP is usually batch updated. So please understand “OLTP data” as “operation datastore content” and “OLAP DATA” as “strategic-analytic datastore content”.

About your question, (sure on instant information?) yes! I am absolutely sure, but I also absolutely refer to "strategic". There are very important decisions that are not strategic, and such decisions shall be addressed by operation application. My accounting system, for example, shall tell me instantly my resources up to last cent. This is very important, I can't survive without such information, but it is operation. A strategic question would be what was the evolution of profitability by product. Knowing that until yesterday or until last minute would make no difference.

I guess you don't work in the Medical or Financial industry.

Medical NO! But 40%+ of our clients are global banks.