SAP Analytics Cloud Lifecycle Management Best Practices – Part 1: How Many Tenants Do I Need?
When it comes to managing the lifecycle of objects in SAP Analytics Cloud (SAC), users have several options to choose from. These options, including the number of tenants, differentiate based on every organization’s unique needs and processes for managing data. When considering these options and choosing a path that’s right for your organization, it’s pivotal to first and foremost, analyze and plan your landscape. In this blog post, I will explain how to properly determine the number of tenants or environments required to efficiently manage the lifecycle of your data.
If you are just starting your SAP Analytics Cloud journey, you are probably asking yourself, “how many SAC tenants do I need for my organization?”. This is a frequently asked question with a different answer for every organization. The simple answer is that you can manage one or multiple tenants. However, SAP Analytics Cloud recommends at least two tenants to efficiently manage the data lifecycle.
To help you navigate your journey effectively and efficiently, let’s dive deeper into this topic and look at key outcomes you can expect depending on the number of tenants to help you make the right decision for your organization.
As mentioned before, the minimum number of tenants that is recommended by SAC to properly implement change control procedures within your business is two. There are a number of advantages for those that decide to use two tenants. For example, one tenant may be used for developing and testing while the second tenant can be utilized for the production content. This enables tighter control of the changes that that take place in your environments, including the ability to use the export/import feature to move changes to production once the testing content is approved. Now, you can seamlessly run numerous changes between both tenants and decrease the risk of ruining sensitive data.
Although multiple tenants are recommended by SAC, some customers start with only one tenant, with valid reasons. Let me explain.
A single tenant can be appropriate for small companies or those in their initial rollout phase, unsure of their exact needs but with the understanding that they could scale up to multiple tenants at a later date. If you choose the single tenant route, it’s critical to handle your content with caution. Unlike a multiple tenant scenario that allows users to test content in a QA environment before transferring it to a production model, a single tenant limits room for error, causing overwriting issues that can occur easily. How? Remember, SAP Analytics Cloud assigns a unique ID to all objects. For the purpose of this example, let us say that you want to import a new version of a content package. Since duplicate objects cannot exist in the system, it is possible to overwrite data when trying to update the package when objects have the same ID. This is one of the most important reasons for requiring two systems to properly manage the data changes.
Single Tenant vs. Multiple Tenants
Hopefully, now you have a better understanding of how to select the right number of systems for your enterprise. To summarize, here are the key differentiators between a single tenant and multiple systems:
The process of determining the number of tenants required is only one piece of establishing a solid lifecycle management workflow in SAP Analytics Cloud. Once you’ve analyzed and planned the structure of your landscape, you can then implement the appropriate structure to meet your needs. As your business requirements and processes evolve, you too could re-evaluate and evolve your landscape to align with them.
If you would like to learn more about lifecycle management in SAP Analytics Cloud, stay tuned for the second part of this blog series. To get additional training for you or your team, discover all of our learning options, curated and delivered by product experts to help you maximize the return on your product investment.
Author: Crystal Vázquez Zambrana