Talk:In-memory processing

Computing Unassessed

This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks. ??? This article has not yet received a rating on Wikipedia's content assessment scale. ??? This article has not yet received a rating on the project's importance scale.

Merger proposal

Latest comment: 11 years ago3 comments3 people in discussion

Original nominator didn't bother to begin a discussion. As for me, I haven't any clear opinion on this merge. --4th-otaku (talk)

My particular opinion on this is that we dont merge these two because they are far too broad in of themselves to be merged, final vote, no. - Joel Wyman Junior — Preceding unsigned comment added by 67.5.252.3 (talk) 23:26, 5 June 2014 (UTC)Reply

Those are two different subjects altogether
Regards, Tshuva (talk) 11:34, 23 June 2014 (UTC)Reply

As it stands, this article can't stay on Wikipedia anyway; it's written like an essay trying to sell you some products, not an informative encyclopedia article. I don't know if there is anything salvageable here, but merging it into another article is one way. Deleting is another way. -- intgr [talk] 14:56, 24 June 2014 (UTC)Reply

This topic is increasingly important because most modern RDBMS support in-memory database functions and users need to understand when and how to use and tune these features. In-memory databases are distinct from in-memory processing by being transactional, by being durable (through durable transaction logs), and by supporting the usual DBMS features such as query languages. Falling DRAM prices have driven major improvements in the cost-effectiveness of in-memory database technologies, and they are now commonly mainstream. MySQL and Oracle have long supported this, and with the 2014 release Microsoft SQL Server also supports it.