Home » RDBMS Server » Performance Tuning » Why use Oracle In-Memory database from another perspective (Oracle In-Memory Database)
Why use Oracle In-Memory database from another perspective [message #665705] Fri, 15 September 2017 22:06 Go to next message
Messages: 4
Registered: August 2017
Junior Member
Why use Oracle In-Memory database from another perspective
A lot of people are talking about why or why not use Oracle In-memory database in their applications and most of them are too focused on the size of the database or whether it is an OLAP application. It seems that small and medium size databases are not suitable for using Oracle In-memory database option. But if your OLTP databases are suffering from performance bottleneck and you are looking for solutions, I think Oracle In-Memory database option should be on your solutions list, especially when you are planning to upgrade your hardware.
Re: Why use Oracle In-Memory database from another perspective [message #665706 is a reply to message #665705] Sat, 16 September 2017 01:05 Go to previous message
John Watson
Messages: 7148
Registered: January 2010
Location: Global Village
Senior Member
I can't understand what your "In-Memory Maestro" tool is showing, that business of "auto 1" means nothing to me. If you want to discuss the use of the In-Memory option in a way that will be meaningful to others, you might consider capturing and displaying execution plans in away that people will understand. There is nothing wrong with selecting the dbms_xplan.display_% functions, you know.
In general though, I find your conclusion astonishing. OLTP work is characterized by small queries and DMLs that use indexed access paths, and the In-Memory option is unusable for these.

And, speaking as a moderator, you need to be careful of making posts in a technical forum that might be better placed in the Marketplace forum. First warning!
Previous Topic: Is there a way to find out activities due to redo logs
Next Topic: Is there a equivalent of delete nologging operations
Goto Forum:

Current Time: Mon Nov 20 15:09:46 CST 2017

Total time taken to generate the page: 0.07190 seconds