Global & Batch Variables Configuration

 How do global or batch variables affect batch execution?

The global and batch configuration variables listed in the following sections directly or indirectly influence the execution of batches. In…

The global and batch configuration variables listed in the following sections directly or indirectly influence the execution of batches. In general, the global variables shown in this section affect all batches.

However, some of these global variables can be overwritten once for the current execution when calling the usp uspBatchExecuteLoadProcessStep (see Manual Batch.sql) or permanently per batch via the configuration of the batches with the ExMeX Companion App.

An overview of the global variables and their current configuration is provided by the view MetadataZone.ConfigExMeXFramework or in the Getting Started -> Configuration section.

Mode of action according to priority

1stVariable passed to the stored procedure uspBatchExecuteLoadProcessStep

2ndVariable configured in the batch(currently via the ExMeX Companion App)

3rdGlobally configured variables

Posted 1 year agoby Dirk.Lerner

How to use variable ExitOnError?

Valid as of release 2.12.0 How a batch behaves within a data pipeline in the case of an LPS error…

Valid as of release 2.12.0

How a batch behaves within a data pipeline in the case of an LPS error can be changed by the variable ExitOnError

ExitOnError: If an error occurs in the batch, the batch is terminated (Exit) or the error is ignored (Off) and the batch continues; Default is to NULL in usp uspBatchExecuteParallelLoadProcessStep (0 = Off, 1 = Exit').

Mode of action according to priority

1stExitOnError Variable passed to the stored procedure uspBatchExecuteLoadProcessStep - e.g. in script ManualBatch.sql

2ndVariable configured in the batch - via the ExMeX Companion App

3rdGlobally configured variables - during installation

If the setting of the batch or the global variable is to take effect, then the parameter @ExitOnError must be set to NULL (@ExitOnError = NULL) or optionally omitted when calling the stored procedure uspBatchExecuteLoadProcessStep! Otherwise, the value passed is always used by the stored procedure as described in the priority order.

ExMeX Companion App

With the ExMeX Companion App, the data modeler can configure individual batch settings for ExitOnError within a batch in the ExMeX Companion App.

From version 0.3.0 it is possible to configure the global variable with the ExMeX Companion App.

ExMeX Framework Core Scripts

Not available.

ExMeX Framework Core Global Variable configuration

To configure this variable, the data modeler or DevOp has to execute the stored procedure MetadataZoneCore.uspConfigExMeXFramework within the ExMeX Framework Core to update the global config variable.

EXEC MetadataZoneCore.uspConfigExMeXFramework
     @VariableName         = 'ExitOnError'
    ,@VariableValue        = '0' 
    ,@VariableDatatype     = 'BIT'   
    ,@VariableDescription  = 'If an error occurs in the batch, the batch is terminated or the error is ignored and the batch continues; 0 = Off, 1 = Exit' 
	

The current settings of all global variables can be checked with the following DML:

SELECT *
FROM MetadataZone.ConfigExMeXFramework

Posted 1 year agoby Dirk.Lerner

How to use variable MaxSqlCommandInChunk?

Valid as of release 2.12.0 How a batch behaves within a data pipeline in the case of executing parallel LPS…

Valid as of release 2.12.0

How a batch behaves within a data pipeline in the case of executing parallel LPS can be changed by the variable MaxSqlCommandInChunk.

MaxSqlCommandInChunk: Defines the max number of LPS which are executed in parallel.

Mode of action according to priority

1stVariable configured in the batch - via the ExMeX Companion App

2ndGlobally configured variables - during installation

ExMeX Companion App

With the ExMeX Companion App, the data modeler can configure individual batch settings for ExitOnError within a batch in the ExMeX Companion App.

From version 0.3.0 it is possible to configure the global variable with the ExMeX Companion App.

ExMeX Framework Core Scripts

Not available.

ExMeX Framework Core Global Variable (during installation)

To configure this variable, the data modeler or DevOp has to execute the stored procedure MetadataZoneCore.uspConfigExMeXFramework within the ExMeX Core Framework to update the global config variable.

EXEC MetadataZoneCore.uspConfigExMeXFramework
     @VariableName         = 'MaxSqlCommandInChunk' 
    ,@VariableValue        = '10' 
    ,@VariableDatatype     = 'INT'
    ,@VariableDescription  = 'Defines the max number of LPS which are executed in parallel.'

The current settings of all global variables can be checked with the following DML:

SELECT *
FROM MetadataZone.ConfigExMeXFramework
Posted 1 year agoby Dirk.Lerner