What are the differences between 11g and 12c Oracle Database?
As a provider of the combined package service Oracle DB Management and Oracle Gold Partner we are often asked: What are the main differences between 11g and the newest 12c Oracle Database.
You ask, we answer! Here are the main features of 12c that differ it from 11g:
The major innovation is the multi-tenancy database. That lets you share common infrastructure between multiple databases. Those are called “pluggable database”. They are “plugged” into a “container” database, which manages the resources. The main purpose of this approach is to make it possible to run many databases on the same hardware. At the same time, you maintain complete security and isolation between the databases. This approach is ideal for cloud deployment.
Here are some of the rest new features of 12c compared to 11g:
Before Oracle users were able to create a single index on one column. With Oracle 12c users can create multiple indexes on the same column. However, the index type must be different and only one type of index is visible at a given time.
Oracle 12c introduces new feature of invisible columns in the table. When a user defines a column as invisible, it won’t appear in generic queries, unless the column is explicitly referred to in the SQL statement or condition, or described in the table definition. However, temporary tables, external tables and cluster tables won’t support invisible columns.
Oracle 12C supports In-memory aggregation, which optimizes the queries that joins the dimension tables to fact tables and aggregate data. User needs to use KEY VECTOR and VECTOR GROUP BY operations to achieve the In-memory aggregation. In memory, aggregation is used in star schema, which improves the performance of Star queries and reduces the CPU usage. The In-memory aggregation eliminates the need of summary tables in most of cases which simplifies the star schema query.
5.Automatic Big table caching:
In previous versions of Oracle, in-memory parallel query did not work well when multiple scans contended for cache memory. The new cache mechanism called big table cache is used to improve the performance for full table scan.
6.Full Database caching:
Caching the entire database provides significant performance benefits, especially for workloads that were previously limited by I/O throughput or response time. More specifically, this feature improves the performance of full table scans by forcing all tables to be cached. This is a change from the default behavior in which larger tables are not kept in the buffer cache for full table scans.
Contact us for additional information and a FREE consultation!contact us