Tired of having to start execution all over again when a connection error occurs?
No need to worry anymore! With an upcoming feature in SR3 called ‘Allow failing data source’ will it be possible to allow a data source to fail if there is a connection error while execution data transfer. This means, that even though a connection error occurs, the execution will not necessarily stop, but instead will it now be setting dependent, selected by the user. The user get to choose between the following options:
1) Fail & stop execution.
2) Continue without data.
3) Continue with existing data.
The first choice “Fail & stop execution” is the same behavior, as you know it today. The execution will stop and an error will occur. If this is the selected setting, then the user will have to start the execution all over again after fixing the error, in order to do a complete execution.
The second choice “Continue without data” will ‘skip’ the current object, and remove any previous instance of data in the raw table, while the valid table content depends on the truncation settings. This setting will continue the execution, even though an error might occur.
The third choice “Continue with existing data” will skip execution of the current object, and remove any previous instance of data from the raw table. The data from the valid table is copied to a temporarily storage, and is reinserted back into the valid table after data cleansing has finished. This setting will continue the execution, even though an error might occur.
This new feature allows you to make a choice of your own when it comes to connection errors. Do you want to start the execution all over again, or allow the execution to continue with previous or no data, and instead come back to do a single execution after fixing the error?
The choice is yours!