Procedure Metadata

SYS.Procedures

This table supplies information about the procedures in the virtual database.

Column Name	Type	Description
`VDBName`	string	VDB name
`SchemaName`	string	Schema name
`Name`	string	Procedure name
`NameInSource`	string	Procedure name in the source system
`ReturnsResults`	boolean	Returns a result set
`UID`	string	Procedure UID
`Description`	string	Description set at the CData Virtuality Server
`OriginalDescription`	string	Description from the data source
`OID`	integer	Unique ID*
`Owner`	string	Name of the procedure owner
`ExecuteAs`	string	Executor of the procedure (`CALLER` or `OWNER`)
`IsFunction`	boolean	Returns `TRUE` if it is a function; `FALSE` if it is a procedure

* The OID column is guaranteed to be unique/consistent unsafe-only for the given version running instance of a VDB. If a different version of the VDB is deployed, these IDs are not guaranteed to be the same or unique across both versions of the VDB. Dynamic VDB OIDs are not cluster-safe.

Owner column in SYS.Procedures available since v4.1

IsFunction column in SYS.Procedures is available since v4.6

SYS.ProcedureParams

This supplies information on procedure parameters.

Column Name	Type	Description
`VDBName`	string	VDB name
`SchemaName`	string	Schema name
`ProcedureName`	string	Procedure name
`Name`	string	Parameter name
`DataType`	string	CData Virtuality Server runtime data type name
`Position`	integer	Position in procedure arguments
`Type`	string	Parameter direction: "`In`", "`Out`", "`InOut`", "`ResultSet`", "`ReturnValue`"
`Optional`	boolean	Parameter is optional
`Precision`	integer	Precision of parameter
`TypeLength`	integer	Length of the parameter value
`Scale`	integer	Scale of parameter
`Radix`	integer	Radix of parameter
`NullType`	string	Nullability: "`Nullable`", "`No Nulls`", "`Unknown`"
`UID`	string	Procedure UID
`Description`	string	Procedure description set at the CData Virtuality Server
`OriginalDescription`	string	Description from the data source
`OID`	string	Unique ID*

* The OID column is guaranteed to be unique/consistent unsafe-only for the given version running instance of a VDB. If a different version of the VDB is deployed, these IDs are not guaranteed to be the same or unique across both versions of the VDB. Dynamic VDB OIDs are not cluster-safe.