Lok, the extra-cost Oracle In-memory feature supports column store
tables/indexes
In-Memory Column Store Architecture
(oracle.com)<https://docs.oracle.com/en/database/oracle/oracle-database/19/inmem/in-memory-column-store-architecture.html#GUID-EEA265EE-8FBA-4457-8C3F-315B9EEA2224>
Mark Powell
Database Administration
(313) 592-5148
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on behalf
of Lok P <loknath.73@xxxxxxxxx>
Sent: Tuesday, September 21, 2021 2:48 PM
To: Oracle L <oracle-l@xxxxxxxxxxxxx>
Subject: Question on IO consideration
Hello Listers, We have oracle exadata databases which are performing mostly
warehousing or batch type data processing. And few are hybrid i.e combination
of both oltp+warehousing/analytics types processing. ETL jobs run on a few of
these which move/read/write billions rows daily. The databases are 50TB to
~150TB in size currently. Few architecture team members suggested evaluating if
we can use columnar database type of offering for IO reduction and thus better
performance considering the future growth. As per my understanding , Oracle
stores data in row format only, so is there any other offering from Oracle for
columnar datastore format or columnar databases and we should evaluate that? Or
is there any clustering kind of technique which can be evaluated which will
help reduce IO? Want to understand experts' views here on this.
Regards
Lok
