Re: [External] : Re: in-memory option - worth it?

I share the same opinion as Mike about the naming, I usually say we should have named it the Analytics Database option or the Columnar Database option since Database In-Memory targets speeding up analytic query performance and not OLTP. People hear in-memory and think it will speed up everything.

Jeff, if you want help or specific questions answered feel free to contact me directly.

Yes, I work for Oracle and I am one of the Database In-Memory Product Managers.

Regards,

Andy Rivenes

> On Apr 15, 2021, at 5:59 PM, Michael Brown <dba_at_michael-brown.org> wrote:
>
> 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_at_gmail.com> 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,

†Ûiÿü0ÁúÞzX¬¶Ê+ƒün– {ú+iÉ^ Received on Fri Apr 16 2021 - 03:10:05 CEST