sp_enum_sqlagent_subsystems

sp_enum_sqlagent_subsystems#

Lists the job step subsystems this Querona instance can execute.

Use it before setting @subsystem on sp_add_jobstep or sp_update_jobstep: those procedures reject any value that is not listed here, and the error they raise names this procedure as the place to look.

The listing is specific to the host. A subsystem backed by a tool that is not installed on that machine is absent, which is the same answer you get if a job step tries to name it.

Syntax#

sp_enum_sqlagent_subsystems

Arguments#

None.

Permissions#

Requires the View any job permission.

Result set#

Column	Type	Description
subsystem	nvarchar(40)	Name to pass as `@subsystem`.
description	nvarchar(512)	What the subsystem does.
subsystem_dll	nvarchar(255)	Always NULL. Querona loads no subsystem libraries.
agent_exe	nvarchar(255)	Always NULL.
start_entry_point	nvarchar(30)	Always NULL.
event_entry_point	nvarchar(30)	Always NULL.
stop_entry_point	nvarchar(30)	Always NULL.
max_worker_threads	int	Always NULL. Subsystems share the scheduler’s workers.
subsystem_id	int	Identifier of the subsystem.

The columns that are always NULL exist for compatibility with the SQL Server result shape. Querona executes a subsystem in-process or through a tool shipped with the product, rather than by loading a subsystem library and calling entry points in it, so those columns have no counterpart.

subsystem_id keeps the SQL Server identifier where the subsystem exists in both products — TSQL is 1 — while subsystems particular to Querona are numbered from 1000 upwards, above the range Microsoft assigns.

Examples#

List everything this instance can run.

EXEC sp_enum_sqlagent_subsystems;

subsystem   description                    ...  subsystem_id
----------  -----------------------------  ---  ------------
KSeF        KSeF, Poland's national ...    ...          1000
TSQL        Transact-SQL                   ...             1