The RETURN_VALUE parameter is not applicable for Microsoft Azure Synapse SQL Connector.

A stored procedure returns output fields that contain only integer values. For example, fields of int, bigint ,tinyint, smallint, and bit data type are returned as output fields.

You cannot have input fields of datetimeoffset, binary, or varbinary data type in a stored procedure.

When you configure a mapping to call a stored procedure in Microsoft Azure Synapse SQL, do not configure an override for the schema. The Secure Agent fails to fetch the metadata from the stored procedure when you specify an override to the schema name.

You cannot read from a stored procedure whose name contains Unicode characters. The mapping fails with an SQL compilation error.

Do not specify more than one SQL query in an SQL transformation. A mapping with multiple SQL queries fails.

You cannot call a stored procedure from an entered query.

If you want to parameterize the connection in an SQL transformation, perform the following steps:

Select a valid non-parameterized connection for the SQL transformation.
Configure the stored procedure or SQL query.
Change the connection to a parameterized connection.

When you use a parameterized connection for a SQL query, you cannot add new output fields.

When the connection and the SQL query point to different schemas, the agent considers the schema specified in the SQL query.