sp_addengine

Adds an engine to an existing engine group or, if the group does not exist, creates an engine group and adds the engine.

Considerations for process mode

sp_addengine does not run in threaded mode.

sp_addengine engine_number, engine_group [, instance_id]

engine_number – is the number of the engine you are adding to the group. Legal values are between 0 and a maximum equal to the number of configured online engines minus one.
engine_group – is the name of the engine group to which you are adding the engine. If engine_group does not exist, the SAP ASE server creates it and adds the engine to it. Engine group names must conform to the rules for identifiers. For details, see Expressions, Identifiers, and Wildcard Characters in Reference Manual: Building Blocks.
instance_id – (in cluster environments) ID of the instance to which you are adding an engine or engine group.

Example 1 – If no engine group is called DS_GROUP, this statement establishes the group. If DS_GROUP already exists, this statement adds engine number 2 to that group:
```
sp_addengine 2, DS_GROUP
```
Example 2 – Adds engine number 5 to instance ID 8:
```
sp_addengine 5, 8
```

There are additional considerations when using sp_addengine:

sp_addengine creates a new engine group if the value of engine_group does not already exist.
If sp_cluster set system_view is set to cluster, you can add an engine or engine group to any instance in the cluster. If system_view is set to instance, you can add and engine or engine group only to a local instance.
The engine groups ANYENGINE and LASTONLINE are predefined. ANYENGINE includes all existing engines. LASTONLINE specifies the engine with highest engine number. A system administrator can create additional engine groups. You cannot modify predefined engine groups.
As soon as you use sp_bindexeclass to bind applications or logins to an execution class associated with engine_group, the associated process may start running on engine_number.
sp_engine can run in sessions using chained transactions after you use sp_procxmode to change the transaction mode to anymode.
Prior to making engine affinity assignments, study the environment and consider the number of nonpreferred applications and the number of SAP ASE engines available. See the Performance and Tuning Guide for more information about non-preferred applications.

The permission checks for sp_addengine differ based on your granular permissions settings.

Setting	Description
Enabled	With granular permissions enabled, you must be a user with `manage any execution class` privilege.
Disabled	With granular permissions disabled, you must be a user with sa_role.

Values in event and extrainfo columns from the sysaudits table are:

Information	Values
Event	38
Audit option	exec_procedure
Command or access audited	Execution of a procedure
Information in `extrainfo`	Roles – Current active roles Keywords or options – NULL Previous value – NULL Current value – NULL Other information – All input parameters Proxy information – Original login name, if set proxy in effect