End Success Component
The "End Success" component can be used to mark the overall status of the job as a success, even if certain parts of it were not successful. It also serves to document the expected end point of a job.
The example below shows when it may be useful to make a job succeed even when parts of it fail.
Only the Name property can be configured to provide a meaningful description of the component.
|Name||Text||A human-readable name for the component.|
In the example below, after the fact table is created some optional housekeeping is run. This housekeeping may, for example, attempt to perform a vacuum on the flights table. Since this housekeeping may fail if another vacuum is running elsewhere on the database, but the data was successfully loaded, a failure of the housekeeping job is not considered fatal and the job will complete successfully.
Without the End Success component called "Treat as Success", a failure of the housekeeping job would instead mark the overall status of this job as a failure.
The End Success component called "Genuine Success" serves as a documented end point of the job but otherwise serves no purpose, since if the "Optional Housekeeping" component ends successfully and there is no more work to do, the overall status of the job will be successful anyway.
The name can be set to a custom value.