SAP HANA Memory Utilization-Corporate Memory _ SCN
-
Upload
arunkumar-thangaraj -
Category
Documents
-
view
13 -
download
1
description
Transcript of SAP HANA Memory Utilization-Corporate Memory _ SCN
-
7/7/2015 SAPHANAMemoryUtilizationCorporateMemory|SCN
http://scn.sap.com/docs/DOC65057 1/5
GettingStarted Newsletters Store
Products Services&Support AboutSCN Downloads
Industries Training&Education Partnership DeveloperCenter
LinesofBusiness UniversityAlliances Events&Webinars Innovation
LogOn JoinUsHi,Guest SearchtheCommunity
Activity Communications Actions
Browse
0 Tweet 0
createdbyRupakNandionJun30,201511:38AM,lastmodifiedbyRupakNandionJun30,201512:09PM
1CorporateMemoryWhileworkingwithbigclientshavingbusinesses throughout theglobe, itbecomesreally important tomanage thedataandwhereverpossible,reducethedatabasesize.Whendealingwithmillionsofrecords,weoftencomeupwithasituationwherethedatabasesizereachesalmostthemaximumcapacityanddataloadingisnolongerpossible.WealwayscannotaskclientincreasetheDBsizeaslotofmoneyisinvolved.EspeciallyifyouareusingHANAdatabase.Several Archiving techniques have been introduced in HANA like NLS and Dynamic Tiering for Using ExtendedTables,butthesearenotonlyexpensivebuthavesomerestriction.ForexampleifadocumentisalreadyachievedusingNLS,thenifyouwanttoloaddeltaofthatrecordintoDSO,youwillcomeupDSOactivationerror.We have a simple technique that can be used easily to reducemainmemory sizewithout incurring toomuch ofimplementcost.HerewearestoringthenotsoimportantdatainseparatememorycalledCorporateMemory.1.1DatainCorporatememoryFirstweneedtoanalyzewhicharethelargetablesinDBACOCKPIT.Thenweneedtotakedecisionbasedonbusinessrequirementwhichdataisnotsoimportant.Dataareclassifiedinto3types:Hot,WarmandColdHotData:Datawhichisregularlyusedandoftenchangede.g.Last3yearsofdataWarmData:Datawhichisrarelyusedandmayneedonceortwiceinaquartere.g.Databetweenyear2012and2006.ColdData:Datawhichismostlikelynevergoingtobeusedbutstillbusinesswantstokeepe.g.databeyond2006.Theproductiondatacanbeclassifiedintothesegroupsbasedonbusinessrequirement.Theselectionfiledcanbetimeorcompanycodeoranything.Itshouldbepurelyabusinessdecision.WithcorporatememoryweintendtokeepbothWarmdataandColddataoutofmainmemoryandthusreducedrasticallythesizeofmainmemoryCreateInflowDSOwhichwillbecopyofthelargeBWtables.1.2HanaDataBaseTounderstandtheadvantagesofcorporatememory,wefirstneedtounderstandhowthedataisstoredintheHANAdatabase.WhenadataisloadedintoanInfoProviderinHANA,itactuallygetsloadedintotwostoragearea:MemoryandDisk.ThusadatawillbeaccessedveryquicklysinceitresidesinmemorylikeRAM.
ThescreenshotsuggeststhatithasgottwoMemories:CurrenttotalMemoryandSizeondiskWithCorporatememoryconcept,wecanoffloadsomeofthedatafromMainmemoryandkeepitonlyindisk,somainmemorysizegetsreduced
SAPHANAMemoryUtilizationCorporateMemory
Share 0Like
Version1
AT00335981Sticky NoteWhile working with big clients having businesses throughout the globe, it becomes really important to manage the data and wherever possible and reduce the data base size.
when dealing with millions of records, we often come up with a situation where the data base size reaches almost the maximum capacity and data loading is no longer possible .
we always cannot ask client increase the db size as lot of money is involved.
Especially if you are using hana database.
several archiving techniques have been introdued in hana like NLS and Dynamic tiering for using extended tables, but these are not only expensive but have some restriction.
For example if a document is already archived using nls, then if you want to load delta of that record into dso, you will come up dso activation error
we have a simple technique that can be used easily to reduce main memory size without incurring too much of implement cost.
Here we are storing the not so important data in separate memory called corporate memory.
AT00335981Highlight
AT00335981Highlight
AT00335981Highlight
-
7/7/2015 SAPHANAMemoryUtilizationCorporateMemory|SCN
http://scn.sap.com/docs/DOC65057 2/5
Unload"SAPMIW"."/BIC/B0002683000"
2Architecture2.1FunctionalDetailsLetstakeanexampleofFIDSO.Weassumethatithasdatafromyear2000to2015.BusinessapprovedthatDataform2012onwardswillonlybeusefulforreportingandrestarehistoricaldataandmaynotrequireoften.HenceDatafromyear2000to2011canbeconsideredasColdandWarmdata.HencethesemaynotberequiredtobekeptinMaunmemory.ThesedatawewillbestoredinInflowDSOandthenwillberemovedfromtheMainDSO.2.2TechnicalDetails
CreateanInflowDSO(CorporateDSO)whichwillbeacopyoftheMainDSO.CreatetransformationandDTPToandFrofrombetweentheCorporateDSOandMaiDSOLoadperiodwiseDatatotheCorporateDSO.(Year2000to2011)OnceDataisloadedintheCorporateDSO,doselectivedeletionofyear2000to2011fromtheMainDSO.InDBACOCKPITrunSQLstatement:
Unload"SAPMIW"."/BIC/AFIXXXXX"(Here/BIC/AFIXXXXXistheactivetableofCorporateDSO)TheabovestatementwilloffloadwholedataofthemainmemoryofcorporateDSO
3DBACOCKPITTest3.1BeforeCorporatememoryLoad
RuntcodeDBACOCKPIT
ExpandCurrentStatus
DoubleclickonOverview
Wewillgettheoveralldatabasesize
3.2CorporatememoryLoad
-
7/7/2015 SAPHANAMemoryUtilizationCorporateMemory|SCN
http://scn.sap.com/docs/DOC65057 3/5
Aftertakingthestatisticsfromthecockpit,weneedtodothesebelowsimplestepsLoadPeriodwisedatatoCorporatememoryDSOfromtheMainDSODoselectivedeletionofDatafromtheMainDSOoftheperiodsthatareloaded.CheckthesizeoftheMainmemorytableinDBACOCKPITInDBACockpit,ExpandDiagnostics,doubleclickontableView
EntertheActiveDatatablenameinTable/ViewSectionandDisplayfind
ThenextscreenwillgiveyouthecurrentsizeoftheCorporatetable
HerewecanseetheMainMemoryishaving1.12GBofdataallocatedforthisDSO
-
7/7/2015 SAPHANAMemoryUtilizationCorporateMemory|SCN
http://scn.sap.com/docs/DOC65057 4/5
3.3OffloadofMainMemory
RunSQLcommandinDBACOCKPITSQLEditor:Unload"SAPMIW"."/BIC/AFIXXXXX"
ExpandDiagnostics
DoubleclickonSQLeditorandenterthecommand
ClickonexecuteAllthedatafromthemainmemoryofthisCorporateDSOwillbedeleted
CheckagainthesizeofthistableinDBACOCKPITTablesView
HerewecanseetheSizeofMemoryisZeroThesizeonDiskRemainssameaswehaveonlydeleteddatafromthemainmemoryandnotfromthedisks
4ImportantNotesandConclusion4.1Notes:
WecanrepeatthisactivityforasmanynoofDSOsorcubethatwewant.Oncewefinishthisactivity,sometimeswecanseethedatagaincomesbacktomainmemoryautomatically.ThisisbeingdonebythesystemifsomeoneeventriestocheckthedataofcorporatememoryinSE11orLISTCUBE.ThishappensbecauseofHANAfunctionalitycalledDELATMERGE.DELATMergeisaHANAstandardfunctionalitywheredeltadataisinitiallystoredinDeltamemory.LatteritismovedtoMainMemory.ToavoidthiswecanrunajobthroughProgramthatwillperformtheoffloadofMainMemoryusingtheaboveSQLcommandonaperiodicbasissothatevenifsomeonedoesopenCorporatememoryDSOs,anddataagainloadedintheMainmemory,thesewillperiodicallydeleteMainMemoryandkeepscheckthesize
-
7/7/2015 SAPHANAMemoryUtilizationCorporateMemory|SCN
http://scn.sap.com/docs/DOC65057 5/5
FollowSCNSiteIndex ContactUs SAPHelpPortalPrivacy TermsofUse LegalDisclosure Copyright
AverageUserRating
(1rating)
0 Tweet 0
4.2Conclusion
AftertheCorporateMemoryactivityisperformedwecanagainchecktheOverallDBACOCKPITsize,youwillseethatthereisamassivereductionThiswillhelptoreallycontroltheMainMemorySizeinthedatabaseandcansavegoodamountofmoneyforthecustomersbuynotaskingtheincreasethesize.ThisisacoastaffectivesolutionandalsohavelessmaintenancecostSelectivedeletionfromtheOriginalDSOhelpsreducethesize.
141Views
Share 0Like
1Comment
Like(1)
LarsBreddemannJul1,20152:09AM
Thereseemtobeamixupoftermshere.CorporateorOrganizationalmemoryWikipedia,thefreeencyclopediaisaconceptforhowanorganizationdealswiththeinformationitproducesandgathers.It'snotthesameasSAPBW,SAPHANAdatabaseorthememoryallocationofanyofthosesystems.WhileyoutrytoexplainmemoryallocationandusageconceptsofSAPHANA,unfortunatelyyoubrushthemtolightly.TablesgetunloadedfromSAPHANAmemoryautomaticallyandPSAtablesevenareprioritizedforthat.Manualunloadisandshouldbetheexception.BesidesthatIthinkyoushouldcontinuewritingblogs.Theideaofprovidinganoverviewonthistopiciscertainlygood.Lars