Given this situation, are there any possible reasons to export data to a NoSQL solution? Maybe Datawarehousing, Analytics, etc.
Any comments are welcome.
Unfortunately, relational models usually do not Are understood (including “relational” DBMS), so instead of these systems reject what they could simply extend.
For various reasons, we have different products that rely on relational databases , Is basically the transactional nature of the operation (atomicity, consistency, etc.). This will not change soon.
Given this situation, is there any possible reason to export data to NoSQL solution? Maybe Datawarehousing, Analytics, etc.
Any comments are welcome.
“Data” is just a vague generalization without data structure. “Relationship” means The data structure is a relation/table with a general query. (It will not automatically interleave the execution of semantic atomic concurrent transactions, which happens to become feasible when the operator of the relation setting is given.) Special data structure or query suggestions are required to increase the relational system interface Or implementation. For various such systems with special case abstraction and/or implementation, “NoSQL” is an all-encompassing one. But they do not need to be non-relational in the interface. They only need content that is not provided by the current “relational” DBMS Given their existence, people can reasonably export (or import from) them when needed.
Unfortunately, relational models are usually not understood (including “relational” DBMS), so instead These systems reject what they could simply extend.