SAP Datasphere Spaces

 


A space is a secure area created by an Administrator, in which members can acquire, prepare, and model data. The Administrator allocates disc and in-memory storage to the space, set its priority, and can limit how much memory and how many threads its statements can consume.

If the administrator assigns one or more Space Administrators as members of the space, they can then assign other members, create connections to source systems, secure data with data access controls, and manage other aspects of the space.

Spaces are virtual work environments with their own data bases. Spaces are decoupled, but are open for flexible access, thus allowing your users to collaborate without having to worry about sharing their data. To model your data and create stories, you need to start off with a space. You can decide how much and what kind of storage you need, as well as how important your space is compared to other spaces. You also add space members and set up connections here.

Each spaces can be created for the modules available. For instance, a space can be created for sales information and other for billing information. These spaces can share their models among themselves. After selecting the models available in the data builder, we can click on share option to share it among different spaces. 

Changing Storage Size: You can change the disk and in-memory storage. Default Sizes: Storage TypeSizeDisk2 GB In-Memory1 GB. The + and - buttons increments or decrements the size by 1 GB.


Space Prioritization: With space prioritizing you can decide how important your space should be treated compared to other spaces. Spaces send queries or jobs to the database. The database then has to decide which job or query has to be dealt with first. Queries from important spaces can be favored, meaning they will be processed faster than queries from other spaces. Spaces with a priority of 8 have the highest available priority. The lowest setting is 1.


Database User: A database user lets you ingest data from third-party SQL tools and allows you to expose your space data to third-party SQL tools.

SAP HANA Cloud Deployment Infrastructure (HDI) Container: provides a service that enables you to deploy database development artifacts to so-called containers. This service describes the deployed (run-time) state of SAP HANA database artifacts - for example, tables, views, or procedures, which have been created or adjusted by the SAP Integrated Development Environment (WebIDE) editors as a family of consistent design-time artifacts for all key SAP HANA platform database features. These artifacts are modeled, staged (uploaded), built, and deployed into SAP HANA Cloud.

Time Dimensions: Enrich your models and stories even further by creating a time-related table for your space. Information such as years, quarters, months and days enrich your models even further by providing additional time-related information. By creating hierarchies based on a specific granularity, time dimensions also allow you to drill down on Stories. You can create a time dimension table within a space, which then allows you to add the time dimensions to your objects in the modeling tools. A time table is created only once per space.



Auditing: Control your data by creating an audit log. You can choose whether you want a read log or a change log to be created for this space. The log files are saved to an SAP HANA audit log. This log has to be mapped to a space if you want to read the data.



Comments

Popular posts from this blog

SAP Datasphere Data Integration - Part 1 - Introduction and Integration using Remote Tables

SAP Datasphere - Data Integration - Part 2 - Data Integration based on Data Flows and External Sources

SAP Datasphere - Data Builder types and creation of Tables