Why Exadata for Oracle Databases?

Many time it comes in our mind that why we should go for Exadata, what benefits we can get if we go for Exadata so here we have given some views based on the Exadata architecture, experience and features. This is the most common question in interview.

No doubt there can be many more advantages than what we have given below as we have only given high level views.

• Exadata is high performance and high available pre-configured device.
• It consists of servers,storage networking and software in single pre-configured box which is massively scalable, secure and redundant.
• Multiple compression tiers are available on Exadata which can help customer to compress data as per business requirement to save storage space.
• Implementation time is very less compare to non-Exadata systems as it's comes as pre-configured and pre-tested.
• In case on any issue with the Exadata than we need to communicate with only single vendor which doesn't required to contact multiple vendor like non-Exadata setup so solution of issue could be done quicker.
• Only DMA (Database Machine Administrator) would be required to manage the Exadata so it can manage with lower TCO which reduce the huge cost of manageability.
• Exadata provides extreme performance for both DW and OLTP databases which is making it and ideal platform for database consolidation.

How to use compression advisor on Exadata?

Compression advisor is used to estimate compression ratio of a particular table by executing compression advisor utility.

Benefits:
It can be used to estimate compression ratio of object/table , based on that we can go for the best possible compression method i.e. OLTP, Query Low, Query High, Archive Low and Archive High.

It also helps us to decide whether we will get optimal benefit of compression or not.

We can come to know how much storage free space we would get if we compress the tables which helps us to do better capacity planning for future requirement.

Following are the steps which need to performed to get the compression ratio of any object.

Oracle Exadata vs IBM Power Systems

Cost comparison for business decision-makers between Oracle Exadata and IBM power system

The FactPoint Group is a Silicon Valley-based research, and consulting firm that is dedicated to the business improvement of its clients.Factpoint Group has conducted survey for Exadata vs IBM Power system with the help of customers as well as technical team who are using these systems.

The research produce TCO comparison for both the systems which includes:

• Acquisition costs
• Implementation and deployment costs
• Operations and maintenance costs for three years.

Below are the major points which were included in the research.

Implementation Cost

As per  research Oracle Exadata require 59% fewer man-hours than the traditional IBM system.

Implementation Time

Implementation of Exadata can be completed within one week where IBM system requires 3 week for implementation.

Operation and Maintenance labor

Exadata Hybrid Columnar Compression (EHCC)

Let's see how EHCC help us to reduce storage space with performance database improvement.

Here we have created three tables with same data as per below.

1. Test  with no compression

2. Test_hcc_archive with archive high compression

3. Test_hcc_query with query high compression

#### List of tables with compression types ####

SQL> select table_name,compression,compress_for

  2    from user_tables

  3   where table_name in ('TEST','TEST_HCC_QUERY','TEST_HCC_ARCHIVE');

TABLE_NAME                 COMPRESS COMPRESS_FOR                            

------------------------------ -------- ------------                            

TEST                           DISABLED                                         

TEST_HCC_ARCHIVE      ENABLED    ARCHIVE HIGH                            

TEST_HCC_QUERY         ENABLED    QUERY HIGH                              

#### Each Tables are with 100000 row data ####

SQL> select count(*) from test;

  COUNT(*)                                                                      

----------                                                                      

    100000                                                                      

Elapsed: 00:00:00.11

SQL> select count(*) from test_hcc_query;

  COUNT(*)                                                                      

----------                                                                      

    100000                                                                      

Elapsed: 00:00:00.10

SQL> select count(*) from test_hcc_archive;

  COUNT(*)                                                                      

----------                                                                      

    100000                                                                      

Elapsed: 00:00:00.10

#### Checking the size of data for each tables ####

Exadata Terms

HP - High Performance

HC - High Capacity

IOPS - IOs Per Second

LUN - Logical Unit Number

MS - Management Server

RS - Restart Server

Cellsrv – Cell Server

SATA - Serial Advanced Technology Attachment

SAS - Serial Attached SCSI

PDU - Power Distribution Unit

ILOM - Integrated Lights Out Manager

IB - InfiniBand

EHCC - Exadata Hybrid Columnar Compression

CU - Compression Unit

UDMs - User Defined Metrics

RDS - Reliable Data Socket protocol

SNMP - Simple Network Management Protocol

iDB - Intelligent Database protocol

EM - Enterprise Manager

EMGC - Enterprise Manager Grid Control

DBRM - Database Resource Manager