By Molly Folan
The 1st of this teaser series is from the session “SAP HANA is moving in! Are your technical landscape and data ready?” which will be presented by Doug Janes from @HP at the @SAPinsider #HANAseminar, kicking off in Chicago July 25-27, 2012.
It’s not that SAP HANA is not scalable; it just requires a different sizing approach than traditional database management systems. Several things need to be considered before implementing SAP HANA, such as the impact on network infrastructures. Another critical factor that must be addressed is selecting the appropriate system based on considerations for future growth, high availability, and disaster recovery capabilities. This is only the beginning of a long list of requirements, precautions, and best practices (offered in the session) to help ensure optimal scalability and performance, but it’s a good starting point and worth keeping in your back pocket if thinking about an SAP HANA implementation.
Key consideration #1: Enterprise applications need more than simple scalability!
- New RDS
- New applications (e.g., SAP NetWeaver BW, SAP ERP)
- New interfaces (e.g., Direct Extractor Connection – DXC)
--Improved backup and recovery
- Add incremental backup<
- Add integration with 3rd party tools
- Backup installation and configuration files (bare metal recovery)
- Initial design complete and undergoing testing
Key consideration #2: Dedicated data network recommended for SAP HANA!
--Source systems should be added to network (same subnet)
- Avoiding routing (layer 3) traffic decreases latency
--Ideally, all systems would connect to same network switch
- Reducing network hops decreases latency
--May require planning hardware upgrades to source systems and network switches
--High speed user network should be considered
- “User” may actually be SAP BusinessObjects or other server requiring high volume data transfers