Planning models are more highly dependent upon the model design.Planning Models using acquired data can require significant resources for both CPU and Memory.Likely to require high CPU than high Memory.Analytic Models using acquired data means the underlying HANA database is used, mostly for read access and so there is a load but it not too heavy.Analytic Models connecting to ‘live’ data sources require minimal hardware resources on SAP Analytics Cloud.Private Editions – a little more about sizing and performance Need to ‘size’ correctly to avoid hitting a hardware limitīut not exclusively since Private Editions have increased database performance protection from other customer services.Typically chosen for larger enterprise deployments.Dedicated database instance reduces impact from other customers’ database activity.Still has some shared components but the core SAP HANA database instance is dedicated.Database performance could be impacted by other customer activity.Internal SAP HANA database instance is shared, with a schema per customer.Public and Private Editions Public and Private Editions Maturity of lifecycle management and change control practices.Options and limitations to promote content between the environments.
Pros/Cons of Quarterly Release and Fast Track Update Release cycles.Any use of SAP Analytics Cloud Test Service and its Preview option.Choice of Public and Private hosted editions.There are many factors that determine the landscape and these include There could be Cloud to On-premise dependencies.May have a desire for fewer Cloud environments to reduce Cloud Service fees.The SAP Analytics Cloud services are updated on a scheduled basis.The role these environments provide remains valid, albeit now with a more obvious associated cost.Still need multiple environments (Sandbox, Dev, QA, Prod).Though some use-cases can be fulfilled solely with SAP Analytics Cloud.So, what changes when working with a Cloud Service?.Each environment (Sandbox, Dev, QA, Prod) has a unique role with regard to the content life-cycle.One for the Business Intelligence or Planning system.‘Traditional’ on-premise landscape environments typically consists of Landscape Architecture: On-premise v Cloud On-premise landscapes