So your company has chosen HANA as a PoC or as a Pilot or even you are using it in anger – so Now WhatHow are you going to install it - Back it up - Move transports – Monitor Performance – Manage data loads.Restaurant StoryI am not going tell you how to do it and expect you to follow it to the letter, but hopefully give you some help on achieving your operational goals
Platform Edition – HANA One (Cloud) and normal database on appliance or on homebrew softwareEnterprise – usually used in Sidecar scenarios – see additional components to get data into the system more effectivelyHANA Solutions – how to get the data out of HANA in a reasonable fashionNot all vendors are created equal, some are better at some things than others – but remember that some HANA skills are very hardware specific, so be care who you engage
This is the single instance – it is usually reserved for Production systems or HANA One systemsIt is a single Appliance with a single schema will be used for Business Suite on HANAAdvantages – no dependencies HANA Sizing is important – all the data storage sizes within the SAP Quick Sizer are based on Uncompressed data – this means that if you are using database compress at the minute then you need to work out your uncompressed size for your database to get an accurate sizing
This is the MCOD scenario – 1 HANA Database with multiple schemas and applicationsAdvantages – better hardware utilisation Never really understood this scenario, in any lifetime!Better Backup and restore scenarios
This is the MCOS scenario – Multiple databases on the same applianceNo virtualisation over head
At it’s core HANA is an SQL database It has tables, columns, rows – it is not magic!BackInt certified Dec 2012
HANA is a platform, it has a number of built in capabilitiesIt has a tomcat web server, R statistical engine and a Server side Javascript engineAll of which need supporting – Can be monitored from the HANA Console, Solution Manager or SQL ScriptsHANA Applications will provide new areas of administration headaches around high capacity performance applications and their architecture that we cannot predict yet!Expect more WebDev solutions to enter into SAP World
Explain a bit more about how it monitors and the Life cycle1 Pilot – no real monitoring required, just snapshot monitoring2. PoC – Turn on initial alerting from and write some scripts for HANA Studio3. Implementation – Turn on Solution Manager alerting – using extended products like LVMDon’t do it – start as you mean to go on in your PoC, use Solution Manager and do not accumulate Technical Debt
More tools to administrate that you have never heard of or even seen
Do you Virtualise the BODS, very difficult question to answer without testingProvides good scalability and powerBottle necks on IO and network which degrade performanceScale up as well as out easilyHow many transformations are the developers doing and are they fixing data as well – these all carry performance cost and there will be a tipping pointBe able to show the performance gains with each iteration, and also the degradation if necessary – not everything is going to work every time
Triggers are only good for Low to medium activity tablesExpect some push back when linking the SLT to non-SAP databases, do your homework and be able to provide volumetrics to the DBAs of the other database – it is professional courtesy!Replication jobs run constantly in the background, and reset the timer after 24 hrs – do not worryThe LTR transaction runs in WBA – so set up Single Sign on
Never used them in anger, but have had a few conversations with people on them
In the time available today - we’ve just touched on some of the technical considerations