k14 Hfm Diet
Short Description
HFM Diet...
Description
The 200or GB diet “how I archived off the first 10 years of my application!”
Michael Malandra
About Edgewater Ranzal
15 Years 700+ clients 1000+ projects
Focus Services People Methodology Customers Partnership
We offer a full spectrum of EPM/BI Services Financial performance, Legal, Segment & Mgmt Reporting, Financial Close HFM Optimization, Performance Lab SOX Compliance Support Installation, Upgrades, Migration, System Monitoring, Backup and Recovery, Disaster Recovery, Load Testing, Hardware Sizing, Exalytics Benchmarking
Business Intelligence
Consolidation
Strategic Finance, Planning, Budgeting, Forecasting, Workforce Planning, Capital Planning, Project Financial Planning
Enterprise Planning Costing & Profitability Mgmt
Infrastructure
Data Integration, Financial Data Management, Data Warehousing, Master Data Management &DRM, ETL Services, Automation
Dashboards & Scorecards, Financial Analytics & Reporting, Operational Analytics, What-if Analysis, Query & Reporting, Visual Exploration
Data Services
Project Management
Training & Support Services
Key Teach Course Delivery: Planning, Essbase, Financial Reporting, Smart View, HPCM, HFM, FDM, DRM, OBIEE Custom Training Delivery: Process & Reporting
HPCM Standard & Detailed Models, Waterfall Allocations, Activity Based Costing, Customer, Product & LOB Profitability
Project/Program Mgmt, EPM Road Maps, Application Reviews, Business Requirements, Process Change, Documentation
Support Services – Infrastructure & Application Support Contracts
To Archive or Not Archive?
Too much of a good thing…
On Average Applications:
that are 2-3 years old can average 10GB to 15GB 25GB to 50GB are also common
100GB to 300GB are rare
500GB and 1TB are mythical
Data Analysis
Determine the current DB/schema size Every Scenario/Year has its own table 1 GB = 1024 MB = 1,073,741,824 Bytes
Before you #egin
A large application doesn’t inherently mean slo!" !emem"er - #B and application per$ormance are independent ●
"%t #B per$ormance can in$l%ence app
Application per$ormance is a $%nction o$ data %sage ●
And r%les& And application tier hard'are&
$an %&M do this automatically' There is no Archive Data" $eat%re(
It’s D(I()( But How?
The patient must minister to himself…
#e$ine )Archive* ● ●
Need to access the historical data Reduce the data set going forward
+reate a second read only )historical* application ,eep only re%ired scenarios ●
Act%al. Act%al at B%dget rates. Act%al at /orecast rates
*is+ Assessment or Lets !ill all the law"ers… Ans'er 2 %estions: 1&
ill go to ail i$ delete this data4
2&
+o%ld "e $ired i$ delete this data4
$ase Study, $odename -enti
11GB o$ data in non-essential scenarios
6&57 o$ the data"ase
#hats $one is $one…
%istorical application 'ill only contain data that 'as reported M%ch smaller application that 'ill not e8pand
Tomorrow% and Tomorrow% and…
To restrict the e8pansion o$ the ne' application. instit%te policies that 'ill limit si9e
,eep /orecasts only 2 years Other scenarios 'ill "e %sed as needed then the data 'ill "e dropped a$ter 12 months
Good &iddance…
Old application 'as 25GB e' Applications are ;3GB A reduction of ..0B or 1 nstit%te policies to prevent gro'th $or non-essential scenarios
*arting is such sweet sorrow…
? sAppame H C? $ sAppame H )e'App* Then Do something…
@lse Do something else…
*ules4 cont(
#oes the r%le $ile have a start "ear varia"le4 ●
$ yes. create a condition in 'hich the varia"le has t'o options sAppame H C? $ sAppame H )e'App* Then nStartYear = “00”
@lse nStartYear = “1""” ●
n not. add an empty year to the "eginning o$ the applicationn12J200K?
Security
ho sees the Cistory4 Maing the App !ead Only ● ●
Mae
View more...
Comments