1 Copyright © 2012, Oracle and/or its affiliates. All ...€¦ · – Fast analytics & reportingFast analytics & reporting ... New features in Oracle Database 12cNew features in

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.1

The following is intended to outline our general product direction. It is intended for information purposes only, anddirection. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasingand should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle. Release timing for Oracle Database 12c is planned for Calendar Year 2013.


Oracle Database 12c

Active

Oracle Database 12cHeat Map, Automatic Data Optimization & In-Database

Frequent Access

Optimization & In-Database Archiving

Occasional Access

Penny AvrilSenior DirectorO l D t b S T h l i Dormant


Oracle Database Server Technologies

Heat Map, Automatic Data Optimization & In-Database ArchivingDatabase Archiving

ChallengesChallenges

Heat Map

A t ti D t O ti i ti ADOAutomatic Data Optimization – ADO

In-Database Archiving


Data Growth Challenges

Opposing forcesOpposing forces- Managing growing volumes of data

cost-effectively- Process data real-time, interactively


Heat MapWhat it tracks

Active

• A “Heat Map” of the Database• Database level Heat Map shows which tables and partitions are

Frequent Access

being used• Block level Heat Map shows last modification at the block level

• Comprehensive

Occasional Access

• Comprehensive• Segment level shows both reads and writes• Distinguishes index lookups from full scans

Dormant

• Automatically excludes stats gathering, DDLs or table redefinitions


Heat Map for Table and Partitions“segment” level trackingsegment level tracking

ORDERS


Heat Map for Blocks“row” level trackingrow level tracking

ORDERS


Heat MapHow to enable

Active Syntax for production..

Frequent Access

SQL> alter system set parameter heat_map=‘ON’;

Occasional Access

SQL> alter table employee ilm enable activity

Syntax for shiphome “121022”..

Dormant

SQL> alter table employee ilm enable activity tracking segment access


Heat MapEnterprise Manager screens Work In Progress, expected GA + 6 monthsp g g , p


Automatic Data OptimizationCompress rows based on usage – “background row compression”Compress rows based on usage background row compression

ORDERS SQL> ALTER TABLE EMPLOYEE ILMADD POLICY ROW STORE COMPRESS ADVANCED ROWAFTER 1 DAY OF NO MODIFICATION


Automatic Data OptimizationCompress partitions based on usage – columnar Exadata onlyCompress partitions based on usage columnar Exadata only

ORDERSSQL> ALTER TABLE ORDERS ILMADD POLICY COMPRESS FORADD POLICY COMPRESS FOR QUERY HIGH SEGMENT AFTER 30 DAYS OF NO MODIFICATIONMODIFICATION


Automatic Data OptimizationOptimize data storage based on usage – columnar Exadata onlyOptimize data storage based on usage columnar Exadata only

ORDERS Optimized use of Row Store & Column Store within a single tableColumn Store within a single table

– Insert / load data as fast as possible –row formatFast analytics & reporting data– Fast analytics & reporting – data optimized in columnar format for analytics


Automatic Data Optimization (ADO)Storage tiering - policyStorage tiering policy

SQL> ALTER TABLE EMPLOYEE ILM ADD POLICY TIER TO LOW COST TABLESPACETIER TO LOW_COST_TABLESPACE


Automatic Data OptimizationStorage tiering – how it worksg g

ORDERS

1. Tables grow in size ILM policies compress dataT bl i iO 2. Tablespace containing partitions reaches ILM tiering threshold

3. Partitions are moved to different tablespace on lower spec disk group


Automatic Data Optimization Optimized Backups with Automated READONLY data movementOptimized Backups with Automated READONLY data movement

Expected syntax for production..

SQL> ALTER TABLE EMPLOYEE ILM ADD POLICY TIER TO DATA2 READ ONLYAFTER 180 DAYS OF NO MODIFICATION


Automatic Data OptimizationOptimized Backups with Automated READONLY data movementp p

ORDERS

1. Tables grow in size ILM policies compress dataT bl i iO 2. Tablespace containing partitions reaches ILM tiering threshold

3. Partitions are moved to new read only tablespaceon lower spec disk group


Automatic Data OptimizationCompetitive

Oracle Storage Vendors

p

Disk Saving Extensive Partial

Performance Speeds Queries Adds OverheadPerformance Speeds Queries Adds Overhead

Integration with

Deep integrationexcludes maintenance tasks Zero integrationIntegration with

Database includes memory access

Integrated with RMAN and Active Data Guard

maintenance tasks considered real access


CompressionNew features in Oracle Database 12cNew features in Oracle Database 12c

Network Compression Faster queries on advanced row (OLTP) compression

Wide tables (>255 columns) for advanced row (OLTP) compression


In-Database ArchivingSpeed up upgrade and reportsp p pg p

• Applications typically work with recent dataApplications typically work with recent data• But often need to retain data for 5 to 10 years

• In-Database Archiving provides the ability to archive infrequently used data within the databasewithin the database

• Archived data is invisible by default• Works with partition pruning and Exadata storage indexes to eliminate I/O for

archived data

• Archived data remains online for SQL Query & DMLs


In-Database ArchivingHow to enableHow to enable

Easily enabled for a table:

alter table

Application can marks rows as archived:

… row archival

update SALES_ORDERS …

set ORA_ARCHIVE_STATE = 1

Sessions can set default visibility to see all data or active data only (default)

alter session set

row archival visibility = [all | active]


row archival visibility = [all | active]

In-Database ArchivingCompetitive

Oracle IBM Optim, Solix, Informatica, HP

A li ti Knowledge Packs for all OracleApplication Knowledge Required

Knowledge Packs for all Oracle Apps. Supports custom rules.

Consultant cost usually required.

N t f f ti litCost No cost for functionality (included in EE) Typical deal in $200K range

Schema Changes Minimal Required (typically shadow Schema Changes Minimal table)

Operational Impact Minimal Access to archive data requires special support, app dev effort


special support, app dev effort

Heat Map, Automatic Data Optimization and In-Database ArchivinggSummary

• Heat Map• Automatically tracks access• Database-aware: maintenance jobs, backups, etc don’t affect heat map

• Automatic Data OptimizationAutomatic Data Optimization• Declarative easy-to-use syntax to define data compression & movement policies• Extensible with business-specific logic

I D t b A hi i• In-Database Archiving• Automatically hide “archive” data from normal users• Keep archive data accessible, minimize impact on storage and performance


The preceding is intended to outline our general product direction. It is intended for information purposes only, and may p p y, ynot be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions The developmentrelied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle. Release timing for Oracle Database 12c is planned for CalendarRelease timing for Oracle Database 12c is planned for Calendar Year 2013.



Documents

1 Copyright © 2012, Oracle and/or its affiliates. All ...€¦ · – Fast analytics & reportingFast analytics & reporting ... New features in Oracle Database 12cNew features in