Stored procedures expose actions other than select, insert, update, and delete that are available in the underlying API.

Using Stored Procedure Schemas

Use stored procedure schemas to generate requests and to validate responses.

Executing Stored Procedures

You can use a send port to execute a stored procedure. You can also use a receive location to execute a stored procedure as an SQL command. See Adapter Configuration for more information on working with receive locations and send ports.

Below is a generated schema for the RefreshOAuthAccessToken command:

<?xml version="1.0" encoding="utf-16" ?> 
<xs:schema xmlns:b="http://schemas.microsoft.com/BizTalk/2003" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.cdata.com/GoogleBigQueryProvider/2020" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="parameters">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="RefreshOAuthAccessToken">
        <xs:complexType>
          <xs:attribute name="OAuthRefreshToken" type="xs:string" /> 
        </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:complexType>
  </xs:element>
  <xs:element name="table">
    <xs:complexType>
      <xs:sequence>
        <xs:element minOccurs="0" maxOccurs="unbounded" name="row">
          <xs:complexType>
            <xs:sequence>
              <xs:element minOccurs="0" name="OAuthAccessToken" type="xs:string" /> 
              
              ...
              
            </xs:sequence>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="AffectedRows" type="xs:int" /> 
    </xs:complexType>
  </xs:element>
</xs:schema>