*Note- We're not “boiling the ocean” here. The Automatic Workload Repository (AWR) is very good at identifying a solid workload and with a worksheet that can adjust for averages and aggregate values, will provide solid estimates to size out the workload for the cloud. Workloads change and in recent years, transactional systems have morphed into hybrid environments with higher IO workloads and better chipsets have offered us better performance with less demand on upgrades.Ĭonsidering the above list, we’re now aware that around 85% of Oracle workloads assessed will require a fraction of the CPU that exists on the on-premises systems.Knowing how budgets work, DBAs should also expect that there is a considerable chance when renewals come up for hardware, that the database won’t receive the funds in the budget and they’ll need to run for longer on the original hardware, so WE PAD the original numbers to prepare for this.DBAs are instructed to size out the on-premises hardware to support the database for 2-7 years and must use both capacity growth values and assumptions to estimate what those resource needs will look like.This results in requirements for on-premises hosts to be larger than required, at the time of purchase. the ability to scale on CPU, like the cloud. How on-premises hardware must be sized- padded to meet resource needs for years vs.It is common for multiple reasons for these hosts to be considerably over-provisioned vs. The reason this doesn’t faze us in the internal team is that we KNOW how on-premises database hosts are sized out for capacity planning.
![oracle database licensing oracle database licensing](https://houseofbrick.com/wp-content/uploads/2015/06/201903_Oracle-License_Workflow.jpg)
Oracle doesn’t appear to make it easy, penalizing hypervisor virtualized CPUs. One of the biggest hurdles to bringing Oracle workloads into a 3 rd party cloud isn’t technology, but licensing hurdles. I get a lot of questions from our field on how the Cloud Architecture and Engineering (CAE) team Oracle SMEs are bringing over so many Oracle workloads to run in Azure so successfully.