Oracle MulBtenant Customer Success Stories

Transcription

1 Oracle MulBtenant Customer Success Stories Mul1tenant Customer Sessions at Customer Session Venue Title SAS Cigna CON6328 Mon 2:45pm SAS SoluBons OnDemand: A MulBtenant Cloud Offering CON6379 Mon 5:15pm Oracle MulBtenant Customer Success Story GE CON7304 Wed 10am Oracle MulBtenant: Seven Sources of Savings Pulte Group CON3203 Wed 3:30pm Finding the Bleeding Edge Without Hemorrhaging Sherwin- Williams CON6387 Wed 4:45pm Oracle MulBtenant Deployment on Oracle Exadata Taleo CON7307 Thu 9:30am Successful MigraBon of Taleo Business EdiBon Cloud Service e- DBA CON2785 Thu noon Rolling Out a PaaS with Oracle MulBtenant HDFC Bank CON3211 Thu 10:45am Deliver Oracle Database Cloud: MulBtenant on SuperCluster 1

2 CON7306 Be]er Together Oracle Mul1tenant Meets Oracle Database In- Memory Maria Colgan Master Product Manager Oracle Database Patrick Wheeler Senior Director, Product Management Oracle Database Safe Harbor Statement The following is intended to outline our general product direcbon. It is intended for informabon purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or funcbonality, and should not be relied upon in making purchasing decisions. The development, release, and Bming of any features or funcbonality described for Oracle s products remains at the sole discrebon of Oracle. 2

3 Agenda Oracle MulBtenant Overview Oracle Database In- Memory Overview MulBtenant + Database In- Memory Use Case: Sandbox Provisioning Agenda Oracle MulBtenant Overview Oracle Database In- Memory Overview MulBtenant + Database In- Memory Use Case: Sandbox Provisioning 3

4 Oracle Database Architecture Requires memory, processes and database files System Resources GL OE AP New MulBtenant Architecture Memory and processes required at container level only System Resources GL OE AP GL OE AP 4

5 Oracle Database Architecture More efficient u1liza1on of system resources System Resources GL OE AP MulBtenant Architecture Components of a Mul1tenant Container Database (CDB) PDBs Root CDB Pluggable Databases MulBtenant Container Database 5

6 Manage Many Databases as One Backup databases as one; recover at pluggable database Level GL OE AP One Backup Point- in- Bme recovery at pluggable database level Manage Many Databases as One with MulBtenant One standby database covers all pluggable databases GL OE AP GL OE AP ProducBon Container Database Standby Container Database 6

7 Simplified Patching and Upgrades Apply changes once, all pluggable databases updated GL OE AP X X X In- place Simplified Patching and Upgrades Flexible choice when patching & upgrading databases GL OE AP GL OE Original Container Database 12.1 Upgraded Container Database 12.x 7

8 Unprecedented Agility with Portable Pluggability PDB migrates through SLAs as it becomes more mission cri1cal GOLD RAC, Data Guard SILVER RAC BRONZE Backups MulBtenant Provides Agility for New Projects Fast Provisioning, Snapshot Clones Seed PDB New PDB From Seed Original PDB Clone of PDB 25 Snapshot 20 Clone of PDB Time Taken to Provision New Database New GL GL- 2 GL- 3 0 Non CDB PDB Snapshot Clone 8

9 Managing Shared Resources Resource management in a mul1tenant environment GL OE AP High Priority Medium Priority Low Priority Advantages of MulBtenant Architecture Reduced CapEx & OpEx, Increased Agility, Easy to Adopt and Use GL OE AP Self- contained PDB for each applicabon ApplicaBons run unchanged Rapid provisioning (via clones) Portability (via pluggability) Common operabons performed at CDB level Manage many as one (upgrade, HA, backup) Granular control when appropriate Complementary to VMs Shared memory and background processes More applicabons per server 9

10 Key Benefits Benefit Minimize CapEx Minimize OpEx Maximize Agility Easy Capability Enabled More applicabons per server Manage many as one (reduced patching!) Standardized procedures & service levels Enable self- service provisioning Snapshot cloning for development and tesbng Portability through pluggability Scalability with RAC To Adopt: ApplicaBons run unchanged To Use: Interface is SQL Agenda Oracle MulBtenant Overview Oracle Database In- Memory Overview MulBtenant + Database In- Memory Use Case: Sandbox Provisioning 10

11 Oracle Database In- Memory Goals Real Time Analytics Accelerate Mixed Workload OLTP No Changes to Applications Trivial to Implement 100x 21 Row Format Databases vs. Column Format Databases Row SALES Transac1ons run faster on row format Example: Insert or query a sales order Fast processing few rows, many columns Column SALES Analy1cs run faster on column format Example : Report on sales totals by region Fast accessing few columns, many rows Un1l Now Must Choose One Format and Suffer Tradeoffs 11

12 Breakthrough: Dual Format Database Memory SALES Row Format Memory SALES Column Format BOTH row and column formats for same table Simultaneously acbve and transacbonally consistent AnalyBcs & reporbng use new in- memory Column format OLTP uses proven row format Oracle In- Memory Columnar Technology Pure In- Memory Columnar SALES Pure in- memory column format Not persistent, and no logging Quick to change data: fast OLTP 2x to 20x compression Enabled at table or parbbon level Available on all hardware plaqorms 12

13 Orders of Magnitude Faster AnalyBc Data Scans Memory CPU Load mulbple region values REGION Vector Register CA CA CA Example: Find all sales in region of CA CA Vector Compare all values an 1 cycle > 100x Faster Each CPU core scans local in-memory columns Scans use super fast SIMD vector instructions Originally designed for graphics & science Billions of rows/sec scan rate per CPU core Row format is millions/ sec Joining and Combining Data Also DramaBcally Faster Example: Find total sales in outlet stores Stores Type Store ID Type=Outlet StoreID in 15, 38, 64 Store ID Sales Amount Converts joins of data in multiple tables into fast column scans Joins tables 10x faster Sum 13

14 Generates Reports Instantly Example: Report sales of footwear in outlet stores Products Footwear Stores Outlets In- Memory Report Outline Footwear $ $$ $$$ $ Sales Dynamically creates in- memory report outline Then report outline filled- in during fast fact scan Reports run much faster without predefined cubes Outlets Sales Complex OLTP is Slowed by AnalyBc Indexes Table 1 3 OLTP Indexes AnalyBc Indexes Most Indexes in complex OLTP (e.g. ERP) databases are only used for analytic queries Inserting one row into a table requires updating analytic indexes: Slow! Indexes only speed up predictable queries & reports 14

15 Column Store Replaces AnalyBc Indexes Table 1 3 OLTP Indexes In- Memory Column Store Fast analytics on any columns Better for unpredictable analytics Less tuning & administration Column Store not persistent so update cost is much lower OLTP & batch run faster Oracle In-Memory: Simple to Implement 1. Configure Memory Capacity inmemory_size = XXX GB 2. Configure tables or partitions to be in memory alter table partition inmemory; 3. Drop analytic indexes to speed up OLTP 15

16 Oracle In-Memory Requires Zero Application Changes Full Func1onality Easy to Implement Fully Compa1ble Fully Mul1tenant - No restricbons on SQL - No migrabon of data - All exisbng applicabons run unchanged - Oracle In- Memory is Cloud Ready Uniquely Achieves All In- Memory Benefits With No Applica1on Changes Agenda Oracle MulBtenant Overview Oracle Database In- Memory Overview MulBtenant + Database In- Memory Use Case: Sandbox Provisioning 16

17 Database In- Memory Works (Be]er) with MulBtenant Mul1tenant consolida1on gives back resources that DB In- Memory needs ConsolidaBon with MulBtenant frees up Memory CPU Cycles Oracle Database In- Memory wants Memory CPU Cycles GL OE AP DB In- Memory Order Fact Column Format In- Memory and Oracle MulBtenant GL OE DW Shared memory and background processes In- Memory Area specified at the container Database level INMEMORY_SIZE=20G By default each Puggable Database inherits the INMEMORY_SIZE from CDB 17

18 In- Memory and MulBtenant INMEMORY_SIZE = 0GB INMEMORY_SIZE = 4GB INMEMORY_SIZE = 16GB GL OE DW INMEMORY_SIZE = 20GB In- Memory and MulBtenant INMEMORY_SIZE = 0GB INMEMORY_SIZE = 10GB INMEMORY_SIZE = 16GB Over subscripbon is possible! GL OE DW INMEMORY_SIZE = 20GB 18

19 Agenda Oracle MulBtenant Overview Oracle Database In- Memory Overview MulBtenant + Database In- Memory Use Case: Sandbox Provisioning AnalyBcs Sandbox Provisioning Provision in an instant; analyze at the speed of thought Product Dimension Produc1on Data Warehouse Industry Dimension Read- Writeable Analy1cs Sandbox DB In- Memory Order Item Fact DW Region Dimension Order Fact Order Fact Column Format ParBBons Quarter Dimension Thinly- Provisioned Sandbox Either full data set Or subset by ParBBon and/or Table 19

20 Oracle MulBtenant Customer Success Stories Mul1tenant Customer Sessions at Customer Session Venue Title SAS Cigna CON6328 Mon 2:45pm SAS SoluBons OnDemand: A MulBtenant Cloud Offering CON6379 Mon 5:15pm Oracle MulBtenant Customer Success Story GE CON7304 Wed 10am Oracle MulBtenant: Seven Sources of Savings Pulte Group CON3203 Wed 3:30pm Finding the Bleeding Edge Without Hemorrhaging Sherwin- Williams CON6387 Wed 4:45pm Oracle MulBtenant Deployment on Oracle Exadata Taleo CON7307 Thu 9:30am Successful MigraBon of Taleo Business EdiBon Cloud Service e- DBA CON2785 Thu noon Rolling Out a PaaS with Oracle MulBtenant HDFC Bank CON3211 Thu 10:45am Deliver Oracle Database Cloud: MulBtenant on SuperCluster 20

21 21