In memory is the worst named option that Oracle has put out in my opinion.
Without knowing what the database is used for, the question of should I get it
is not really possible to answer.
Column Store or Column Store Cache would have been a better name. The option
will not do much for an OLTP system. OLTP transactions will use the same
buffer cache they always have, but a table marked for in memory will also be
maintained organized by columns rather than rows but only in memory (hence the
name) which means aggregate queries will be vastly improved. Read Jonathan’s
blog entries that have already been mentioned. Blogs.oracle.com also has a
blog from the in memory group.
--
Michael Brown
On Apr 15, 2021, at 12:10 PM, Jeff Chirco <backseatdba@xxxxxxxxx> wrote:--
Hey curious if any have the In-Memory option and would it be worth it? We are
looking to increase our CPU footprint on our server and think about maybe
trying to squeeze this in if the discount is right. Although this is the most
expensive option. We are currently a small server, only 4cpu going to 8, but
we also have a DR server which would stay on a 4cpu server but I know it also
needs to be licensed.
What time of systems is it best for? Any good blogs on it?
Thanks,
