OCI Foundations - Database: Difference between revisions
Appearance
	
	
NickPGSmith (talk | contribs)  | 
				NickPGSmith (talk | contribs) m 8 revisions imported  | 
				||
| (2 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
Exadata Database Service on dedicated infrastructure  | Exadata Database Service on dedicated infrastructure  | ||
* For Oracle databases  | * For Oracle databases  | ||
*   | * Co-managed: customer manages DB, Oracle manages infrastructure  | ||
Autonomous Database on Shared and dedicated Exadata Infrastrure:  | Autonomous Database on Shared and dedicated Exadata Infrastrure:  | ||
| Line 19: | Line 19: | ||
== Autonomus DB ==  | == Autonomus DB ==  | ||
Uses machine learning to implement tuning, backups, patching/upgrades  | Self-Driving:  | ||
* Uses machine learning to implement provisioning, tuning, backups, patching/upgrades  | |||
Self-Repairing:  | |||
* Detects and corrects issues including hardware, software, and human errors, helping to maintain high availability and protect against data loss  | |||
Shared or Dedicated use of Exadata hardware.  | Shared or Dedicated use of Exadata hardware.  | ||
Latest revision as of 04:53, 8 May 2024
Introduction
Base Database Service:
- Create on VM with block storage
 - Provisioning service
 
Exadata Database Service on dedicated infrastructure
- For Oracle databases
 - Co-managed: customer manages DB, Oracle manages infrastructure
 
Autonomous Database on Shared and dedicated Exadata Infrastrure:
- Self manaaging and repairing
 - Shared or dedicated infrastructure
 
Cloud@Customer:
- At customer datacentre
 - Exadata Database Service or Autonomous Database on Exadata
 
Autonomus DB
Self-Driving:
- Uses machine learning to implement provisioning, tuning, backups, patching/upgrades
 
Self-Repairing:
- Detects and corrects issues including hardware, software, and human errors, helping to maintain high availability and protect against data loss
 
Shared or Dedicated use of Exadata hardware.
- Autonomous Transaction Processing
 - Autonomous Data Warehouse
 
Autonomous JSON Database:
- Designed for noSQL applications
 - APEX Service
 
MySQL Database Service
Host MySQL in the Cloud:
- Standalone, or
 - High Availablty: 3 nodes providing auto failover to a secondary instance
 
MySQL with HeatWave
- Order of magnitude performance improvements
 - In-memory cache
 - Enables OLTP and OLAP from the same database; no need for a separate OLAP database
 - Exclusive to OCI
 
NoSQL Database
- Fully Managed
 - Elastic
 - High Performance
 - Data model flexibility
 - Access Control
 - Low cost
 - Developer freindly APIs
 - Always available
 - Hybrid cloud/on-premise
 
Uses cases: many where high volumes of data are involved