Saving and Deploying Objects
Save objects to the SAP Datasphere design-time repository, and then deploy your changes to the runtime.
Save an Object
When you save an object, it is stored in the SAP Datasphere repository, which contains the design-time definitions of all your objects.
Create a Copy of an Object
-
Selecting the object in the Repository Explorer and clicking Duplicate.
-
Opening the object in its editor and clicking
Deploy an Object
All Data Builder objects must be deployed to be used productively. When you deploy an object, you create a run-time version for use in SAP Datasphere's underlying SAP HANA database.
-
Compare the design-time and run-time versions and, if there are differences, deploy the design-time version to the runtime. It will change the object's status to Deployed and augment its version number.
For more information, see Reviewing and Restoring Object Versions).
-
Review the deployment status of all the objects in the selected object's lineage, and deploy any that do not already have a status of Deployed to ensure run-time consistency.
For more information, see Impact and Lineage Analysis
-
Remote tables imported into the repository from a source system, database user schema or HDI container (see Importing Tables and Views from Sources).
-
Tables created by importing data from a *.csv file (see Creating a Local Table from a CSV File).
Deployment Status
-
- The object has never been deployed and exists only as a design-time artifact.
-
- The object is deployed to the run-time database and its design-time and run-time versions are identical.
-
- The design-time version of the object contains changes that need to be deployed to make them available in the run-time.
-
(Design-Time Error) - The design-time version of the object is invalid. You can save an object with design-time errors, but you cannot deploy it. To correct design-time errors, review each of the validation messages in the editor, make the necessary changes, and then save the object.
-
(Run-Time Error) - The run-time version of the object is invalid and can no longer be used. Run-time errors may be caused by changes in one or more of the object's sources (see Modifying Objects That Have Dependent Objects). To correct the errors, review each of the validation messages in the editor, make the necessary changes, and then save and deploy the object.
Save Anyway and Deploy Anyway
When you try to save or deploy your object, the Validation Messages dialog opens to allow you to review these messages. You can still save or deploy your object (by clicking Save Anyway or Deploy Anyway), but you should aim to review and resolve these impacts as soon as possible. For more information, see Modifying Objects That Have Dependent Objects.
Debug View Deployment Issues with the View Analyzer
If your view contains very complex calculations or subqueries, includes multiple unions of large views, or has a complicated or deep dependency tree, then you may encounter performance issues (or even, very occasionally, out of memory errors) when deploying.
In such situations, you may be able to improve deployment performance or resolve the errors by persisting one or more of your view's sources. We recommend that you use the View Analyzer and look at the peak memory usage and duration values to guide you in these decisions (see Exploring Views with View Analyzer).


