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

  • January 24, 2018

Planning or Performing an Advanced Compression Proof of Concept? Start Here!

Gregg Christman
Product Manager

In my last blog we discussed a common question regarding Advanced Compression. Before we continue discussing the other common questions (in future blogs) I thought it would be useful to point out a new Advanced Compression white paper that I believe is very useful to organizations planning (or currently performing) a proof of concept (PoC) with Advanced Compression.

The document is not meant to be a step-by-step guide to performing a compression PoC. Instead, this document provides best practices learned from customer PoC’s and provides insights (about Advanced Compression) to help plan your compression PoC, as well as help you understand the results of your PoC.

Some of the topics discussed in the document, that I believe are useful to know for your Advanced Compression PoC, includes:

  • Enabling Advanced Row Compression
  • When Advanced Row Compression Occurs
  • Direct-Path versus Conventional-Path Inserts
  • Index Key Compression and Advanced Index Compression
  • What to Consider for Before PoC Testing Begins
  • Direct-Path and Conventional-Path Loads and AWR
  • RMAN Compression
  • More about Compression, Performance and Compression Ratios
  • What does the Typical Compression PoC Look Like?
  • Compression Advisor
  • Example of Compression PoC as a Multi-Step Process

The document is available on the Oracle Technology Network (OTN) at the link below:

Oracle Advanced Compression Proof-of-Concept (POC) Insights and Best Practices

I hope you find this white paper informative. In my next blog(s) we will discuss additional common compression questions. The database storage optimization continues!

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.