Help · section 6 of 44

Stored Procedures

Mirrors the in-app Help. The live copy in your console and `dlake guide help` are always current.

Create/edit/drop stored procedures in your schema. Procedures can be exposed through the API as execute-entities (execute_entity over MCP, POST over REST). A procedure can also be published to AI agents as its own named tool — see Stored Procedures as MCP Tools. System procedures are protected. Creating, altering, or dropping a procedure does not auto-restart the engine — click Regenerate / Restart DAB to apply it to the Data API. Like a new table, a new procedure is not reachable from the Data API or the MCP data plane until it is both exposed in the Global Scope and picked up by a restart.

Parameter names must start with @. Over the CLI/MCP, create_procedure --parameters rejects {"name":"CustomerName"} with “must start with ’@’” — write {"name":"@CustomerName"}. Each entry is { name, dataType, maxLength?, direction? } (dataType, not type; direction is INPUT or OUTPUT).