sp_dropengine does not run in threaded mode.
Drops an engine from a specified engine group or, if the engine is the last one in the group, drops the engine group.
sp_dropengine engine_number [,engine_group] [,instance_id]
is the number of the engine you are dropping from the group. Values are between 0 and a maximum equal to the number of configured online engines, minus one.
is the name of the engine group from which to drop the engine.
(Cluster environments only) Is the ID of the instance from which you are dropping an engine or engine group.
Drops engine number 2 from the group called DS_GROUP. If it is the last engine in the group, the group is also dropped:
sp_dropengine 2, DS_GROUP
(Cluster environments only) Drops engine number 5 from instance id 8:
sp_dropengine 5, 8
sp_dropengine can be invoked only from the master database.
If engine_number is the last engine in engine_group, Adaptive Server also drops engine_group.
In cluster environments – if sp_cluster set system_view is set to cluster, you can drop an engine or engine group from any instance in the cluster. If the system_view is set to instance, you can drop an engine or engine group only from a local instance.
sp_dropengine can run in sessions using chained transactions after you use sp_procxmode to change the transaction mode to anymode.
The engine_number you specify must exist in engine_group.
The permission checks for sp_dropengine differ based on your granular permissions settings.
Granular permissions enabled |
With granular permissions enabled, you must be a user with manage any execution class privilege. |
Granular permissions disabled |
With granular permissions disabled, you must be a user with sa_role |
Values in event and extrainfo columns from the sysaudits table are:
Event |
Audit option |
Command or access audited |
Information in extrainfo |
|---|---|---|---|
38 |
exec_procedure |
Execution of a procedure |
|
System procedures sp_addengine
