X

Database Storage Optimization best practices, tips and tricks and guidance from Database Compression Product Management

Lets Talk Oracle Compression at Open World - Session CON6410

Gregg Christman
Product Manager

https://blogs.oracle.com/In-Memory/resource/OOW_2016_banner.png

Don't
miss the opportunity to chat with the Oracle Database Advanced Compression team
at one of our sessions or at the Oracle demogrounds.

In
my first session I’ll be sharing best practices, tips, and insights I’ve
gathered from compression users across the globe, regarding data, index, LOBs
and Oracle Recovery Manager backup compression. Even if you already use Oracle
Advanced Compression or Oracle Hybrid Columnar Compression, this session will
provide new insights about how to get best from Oracle compression and ILM.

Tuesday,
September 20th at 11:00am

Getting
the Most out of Database Compression and Information Lifecycle Management

Session
CON6410 at Moscone South - room 301

In
my second session join me, and Database In-Memory Product Manager Andy Rivenes, to
learn how to define both heat map-based and custom policies to control the
population and eviction of objects, as well as the recompression of objects to
a higher level within the Oracle Database In-Memory column store. We’ll also
talk about on-disk Heat Map and ADO compression tiering and storage tiering.

Wednesday,
September 21st at 11:00am

Using
Automatic Data Optimization with Oracle Database In-Memory and Storage-Based
Tiering

Session
CON6412 at Moscone South - room 301

If
you have any questions related to Oracle Advanced Compression, you can ask them
at the Advanced Compression and Database Storage Optimization demo booth (SDB
035) in the Database area of the demogrounds in Moscone South. Members of the
Advanced Compression development team will be there Monday to Wednesday from
9:45am until 5:30pm.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.