Oracle Capacity Planning And Sizing Spreadsheets [NEW]
Oracle Tips by Burleson Consulting Reliable capacity planning for Oracle The easiest way to perform Oracle capacity planning is with the Oracle capacity planning spreadsheets. Determining the future size of Oracle tables, the size of Oracle indexes, and the overall tablespace size is a formidable challenge which depends on many factors:
Oracle Capacity Planning And Sizing Spreadsheets
The concept behind capacity planning is simple, but the mechanics are harder. Capacity planning acknowledges that the business requirements on the system may increase, and forecasts how much resource must be added to the database system to ensure that the user experience continues uninterrupted.
This makes capacity planning different to performance tuning, because the latter is a reactive process. You tweak the system's parameters to ensure that it does not dip below pre-set levels based on current performance requirements. You plan capacity to ensure that it does not fall below performance levels in the future.
These thresholds will help you to monitor when your resource capacity is starting to fall behind. As the number of critical alerts increases, it'll be a good sign that your capacity planning model needs to be revised, and new resource potentially added.
Capacity planning isn't the easiest of tasks for Oracle DBAs, and statistical modelling is never a completely sure thing. The further out you try to plan, the less accurate your details may become, which is why regular revision of your statistical data and recalculation of capacity baselines is a good idea.
Caution - These are extremely powerful undocumented Oracle capacity spreadsheets. They should only be used by a certified Oracle DBA, and after a careful review of spreadsheet sizing and capacity planning assumptions. USE AT YOUR OWN RISK.
Database sizing for Oracle tips Oracle Database Tips by Donald BurlesonMarch 2, 2015 Question: How to I do database sizing for Oracle? Answer: The easiest way to perform database sizing for Oracle is with the Oraclecapacity planning spreadsheets.
Oracle database sizing estimation Oracle Tips by Burleson Consulting Oracle database sizing and estimation are critical for disk capacity planning. Mike Ault has some great Oracle database sizing spreadsheets, and these are the ones used by professionals Oracle consultants to size an Oracle database. Mike put a huge amount of work into them and they are great for Oracle capacity planning: -books.com/download_sizi...preadsheets.htm
Disk-space planning is just one element of the broader discipline of sizing and capacity planning. Sizing (also called pre-configuration capacity planning) takes place before you design the system and attempts to estimate the resources the system will need, over a period of time, in order to meet the conditions of the Service Level Agreement (SLA), or similar specification. At this stage, no statistics exist and so you need to create them, by modelling the system that needs to be designed, which can be quite expensive, or else find other ways to estimate the required resources.
For disk space, and for the number of I/O operations per second, the knee of the curve on the utilization graph occurs at 80-85% capacity. As such, your database should not occupy more than 85% of total disk space; and the number of I/Os per sec. should not regularly exceed 85% of its maximum. These factors must be considered in your planning calculations.
But how do you go about sizing your system? You must first understand how much throughput capacity is required for your system and how much throughput each individual CPU or core in your configuration can drive, thus the number one task is to calculate the database space requirement in your data warehouse.
To size an Oracle database you can estimate a current database of similar size as the one you will need in your new application. You can also use capacity planning to find out how much space you will need for a new Oracle database.
Sprint planning may be split into two separate phases: the WHAT meeting and the HOW meeting. During the WHAT meeting, the sprint goal is defined, the sprint backlog is created, and team capacity is decided. During the HOW meeting, the Scrum team creates the list of tasks needed to complete each backlog item. In software, these tasks typically span design, implementation, testing, and documentation, and each should take no more than a couple of days to complete. If a task does take more than a couple of days, it indicates that the items on the sprint backlog are too large for sprint work; they may need to be split up.
You should also hold a pre-planning meeting with representatives from the Scrum team, Scrum master, and project owner. This meeting, held a few days before the main sprint planning meeting, gives everyone the chance to groom the backlog. Backlog grooming is the process of prioritizing, estimating, detailing, and determining acceptance criteria for backlog items. It expedites the planning session itself and allows for greater productivity during a sprint by more accurately matching the amount of work required with the capacity available.
This is the first blog in the Azure Site Recovery for BCDR and Migration series. If you are planning an On-Premises (VMware) to Azure migration, or are planning to leverage Azure Site Recovery (ASR) in your business continuity and disaster recovery (BCDR) strategy, and want to assess your readiness for Azure, read on.Using Azure-provided Assessment and Discovery tools will give you a deep insight into capacity planning, plan your DR strategy, help you to develop a phased approach to your Azure migration strategy and guide you through initial replication (IR) batching and bandwidth analysis, to help meet your desired Recovery Point Objective (RPO).In this post we take a detailed look at two powerful tools the Azure Cloud offers: