In the Business Catalog are now filtered by type and semantic usage.
For more information, see Business Catalog.
Modeling – Business Layer
You can now use objects which are shared across spaces to build your models in the Business Builder.
In an agile business world, changed requirements might lead to the need of changing object definitions in your systems. For remote tables that have been created during SAP BW/4HANA model import, SAP Data Warehouse Cloud is now able to handle such changes. When underlying sources of remote tables change their column definitions, you can now easily update the remote tables when re-importing the model. For more information, see Importing SAP BW/4HANA Models.
Modeling – Data Layer
You may improve your view performance by activating OLAP hint, particularly if a union is performed.
You may improve the model’s performance by entering join cardinalities. For more information, see Creating a Join.
You can now see who created a space and when. You see the “created by” and “created on” information underneath the general settings when you open your space details.
With the Remote Query Monitor now available in the Data Monitor Integration, you can monitor the communication between the federation layer of SAP HANA Cloud and the connected remote source systems. This provides better insight for analysis of performance bottlenecks and error communications while running federated queries in SAP Data Warehouse Cloud . For more information, see Monitoring Remote Queries.
The job scheduling component of SAP Data Warehouse Cloud runs scheduled tasks on behalf of the owner of the schedule. Per default, the user who creates a schedule is the owner of the schedule. You can now change the owner if required to make sure that scheduled tasks continue to run smoothly when a user left the organization, for example. For more information, see Change Owner of a Schedule.
Whenever you need to upgrade or patch your SAP HANA Smart Data Integration Data Provisioning agent, or you need to apply any changes to its configuration, you can do that without impacting your active real-time replications. Just pause real-time replication for all connections that use the agent all at once, apply the changes to your agent, and restart real-time replication. For more information, see Pause Real-Time Replication for an Agent.
You can now configure a password policy for your database users and apply it to selected users. The current available password policy is to set an expiration time for passwords. For more information see Configuring Password Policies.