sp_dropengine

Drops an engine from a specified engine group or, if the engine is the last one in the group, drops the engine group.

Considerations for process mode

sp_dropengine does not run in threaded mode.

Syntax

sp_dropengine engine_number [,engine_group] [,instance_id]

Parameters

Examples

Usage

There are additional considerations when using sp_dropengine:
  • You can invoke sp_dropengine only from the master database.

  • If engine_number is the last engine in engine_group, SAP ASE also drops engine_group.

  • (Cluster Edition only) If you set sp_cluster set system_view to:
    • cluster – you can drop an engine or engine group from any instance in the cluster.

    • 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.

Permissions

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

SettingDescription
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

Auditing

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

InformationValues
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

Related reference
sp_addengine