Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: Connect to SQL Databases from Workflows description: Learn how to connect to SQL databases from workflows in Azure Logic Apps by using the SQL Server connector. services: logic-apps ms.suite: integration ms.reviewer: estfan, azla ms.topic: how-to ms.date: 06/19/2025 ms.custom: sfi-image-nochange ## As a developer, I want to access my SQL database from my logic app workflow. --- # Connect to SQL databases from workflows in Azure Logic Apps [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)] This guide shows how to access your SQL database from a workflow in Azure Logic Apps by using the SQL Server connector. You can then create automated workflows that run when triggered by events in your SQL database or in other systems, and run actions to manage your SQL data and resources. For example, your workflow can run actions that get, insert, and delete data or that can run SQL queries and stored procedures. Your workflow can check for new records in a non-SQL database, do some processing work, use the results to create new records in your SQL database, and send email alerts about the new records. If you're new to Azure Logic Apps, see the following articles to get started: * [What is Azure Logic Apps?](../logic-apps/logic-apps-overview.md) * [Quickstart: Create an example Consumption logic app workflow using the Azure portal](../logic-apps/quickstart-create-example-consumption-workflow.md) * [Create an example Standard logic app workflow using the Azure portal](../logic-apps/create-single-tenant-workflows-azure-portal.md) ## Supported SQL editions The SQL Server connector supports the following SQL editions: * [SQL Server](/sql/sql-server/sql-server-technical-documentation) * [Azure SQL Database](/azure/azure-sql/database/sql-database-paas-overview) * [Azure SQL Managed Instance](/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview) ## Connector technical reference The SQL Server connector has different versions, based on [logic app type and host environment](../logic-apps/logic-apps-overview.md#resource-environment-differences). | Logic app | Environment | Connector version | |-----------|-------------|-------------------| | **Consumption** | Multitenant Azure Logic Apps | Managed connector, which appears in the connector gallery under **Shared**. For more information, review the following documentation: <br><br>- [SQL Server managed connector reference](/connectors/sql) <br>- [Managed connectors in Azure Logic Apps](managed.md) | | **Standard** | Single-tenant Azure Logic Apps and App Service Environment v3 (Windows plans only) | Managed connector, which appears in the connector gallery under **Shared**, and built-in connector, which appears in the connector gallery under **Built-In** and is [service provider-based](../logic-apps/custom-connector-overview.md#service-provider-interface-implementation). The built-in connector differs in the following ways: <br><br>- The built-in connector can directly connect to a SQL database and access Azure virtual networks by using a connection string without an on-premises data gateway. <br><br>For more information, review the following documentation: <br><br>- [SQL Server managed connector reference](/connectors/sql/) <br>- [SQL Server built-in connector reference](/azure/logic-apps/connectors/built-in/reference/sql/) <br>- [Built-in connectors in Azure Logic Apps](built-in.md) | ### Limitations For more information, review the [SQL Server managed connector reference](/connectors/sql/) or the [SQL Server built-in connector reference](/azure/logic-apps/connectors/built-in/reference/sql/). ## Prerequisites * An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn). * [SQL Server database](/sql/relational-databases/databases/create-a-database), [Azure SQL Database](/azure/azure-sql/database/single-database-create-quickstart), or [SQL Managed Instance](/azure/azure-sql/managed-instance/instance-create-quickstart). The SQL Server connector requires that your tables contain data so that the connector operations can return results when called. For example, if you use Azure SQL Database, you can use the included sample databases to try the SQL Server connector operations. * The information required to create a SQL database connection, such as your SQL server and database name. If you're using Windows Authentication or SQL Server Authentication to authenticate access, you also need your user name and password. You can usually find this information in the connection string. > [!IMPORTANT] > > If you use a SQL Server connection string that you copied directly from the Azure portal, you need to manually > add your password to the connection string. For sensitive information, such as this string, make sure to use the > most secure authentication flow available. Microsoft recommends that you authenticate access to Azure resources > with a [managed identity](/entra/identity/managed-identities-azure-resources/overview) when possible, and assign > a role that has the least privilege necessary. > > If this capability is unavailable, make sure to secure connection strings through other measures, such as > [Azure Key Vault](/azure/key-vault/general/overview), which you can use with [app settings in Standard workflows](../logic-apps/edit-app-settings-host-settings.md). > You can then [directly reference secure strings](../app-service/app-service-key-vault-references.md), such as connection > strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define > app settings within your [Standard logic app workflow definition](/azure/templates/microsoft.logic/workflows). > You can then capture dynamically generated infrastructure values, such as connection endpoints, storage strings, and more. > For more information, see [Application types for the Microsoft identity platform](/entra/identity-platform/v2-app-types). * For a SQL database in Azure, the connection string has the following format: `Server=tcp:{your-server-name}.database.windows.net,1433;Initial Catalog={your-database-name};Persist Security Info=False;User ID={your-user-name};Password={your-password};MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;` 1. To find this string in the [Azure portal](https://portal.azure.com), open your database. 1. On the database menu, under **Properties**, select **Connection strings**. * For an on-premises SQL server, the connection string has the following format: `Server={your-server-address};Database={your-database-name};User Id={your-user-name};Password={your-password};` * In Standard workflows, to use the SQL built-in triggers, you must enable change tracking in the table where you want to use the trigger. For more information, see [Enable and disable change tracking](/sql/relational-databases/track-changes/enable-and-disable-change-tracking-sql-server). * The logic app workflow where you want to access your SQL database. To start your workflow with a SQL Server trigger, you have to start with a blank workflow. To use a SQL Server action, start your workflow with any trigger. <a name="multitenant-or-ise"></a> * To connect to an on-premises SQL server, the following extra requirements apply, based on whether you have a Consumption or Standard logic app workflow. * Consumption workflow: In multitenant Azure Logic Apps, you need the [on-premises data gateway](../logic-apps/logic-apps-gateway-install.md) installed on a local computer and a [data gateway resource that's already created in Azure](../logic-apps/logic-apps-gateway-connection.md). * Standard workflow: You can use the SQL Server built-in connector or managed connector. * To use Microsoft Entra authentication or managed identity authentication with your logic app, you have to set up your SQL Server to work with these authentication types. For more information, see [Authentication - SQL Server managed connector reference](/connectors/sql/#authentication). * To use the built-in connector, you can authenticate your connection with either a managed identity, Microsoft Entra ID, or a connection string. You can adjust connection pooling by specifying parameters in the connection string. For more information, review [Connection Pooling](/dotnet/framework/data/adonet/connection-pooling). * To use the SQL Server managed connector, follow the same requirements as a Consumption logic app workflow in multitenant Azure Logic Apps. For other connector requirements, review the [SQL Server managed connector reference](/connectors/sql/). <a name="add-sql-trigger"></a> ## Add a SQL Server trigger The following steps use the Azure portal, but with the appropriate Azure Logic Apps extension, you can also use the following tools to create logic app workflows: * Consumption workflows: [Visual Studio Code](../logic-apps/quickstart-create-logic-apps-visual-studio-code.md) * Standard workflows: [Visual Studio Code](../logic-apps/create-standard-workflows-visual-studio-code.md) ### [Consumption](#tab/consumption) 1. In the [Azure portal](https://portal.azure.com), open your Consumption logic app resource. 1. On the resource sidebar menu, under **Development Tools**, select the designer to open your blank workflow. 1. Add the [**SQL Server** managed trigger](/connectors/sql/#triggers) that you want for your scenario by following the [general steps to add a trigger](../logic-apps/create-workflow-with-trigger-or-action.md?tabs=consumption#add-trigger). This example continues with the **SQL Server** trigger named **When an item is created**. 1. If prompted, provide the [information for your connection](#create-connection). When you're done, select **Create new**. 1. After the trigger information box appears, provide the necessary information required by [your selected trigger](/connectors/sql/#triggers). For this example, in the trigger named **When an item is created**, provide the values for the SQL server name and database name, if you didn't previously provide them. Otherwise, from the **Table name** list, select the table that you want to use. Select the **Frequency** and **Interval** to set the schedule for the trigger to check for new items. :::image type="content" source="media/connectors-create-api-sqlazure/when-item-created-consumption.png" alt-text="Screenshot shows Consumption workflow designer and managed action named When an item is created." lightbox="media/connectors-create-api-sqlazure/when-item-created-consumption.png"::: 1. Add any other available parameters that you want from the **Advanced parameters** list. This trigger returns only one row from the selected table, and nothing else. To perform other tasks, continue by adding either a [SQL Server connector action](#add-sql-action) or another action that performs the next task that you want in your logic app workflow. For example, to view the data in this row, you can add other actions that create a file that includes the fields from the returned row, and then send email alerts. To learn about other available actions for this connector, see the [SQL Server managed connector reference](/connectors/sql/). 1. When you're done, save your workflow. On the designer toolbar, select **Save**. ### [Standard](#tab/standard) 1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource. 1. On the resource sidebar menu, under **Workflows**, select **Workflows**, and then select your blank workflow. 1. On the workflow sidebar menu, under **Tools**, select the designer to open your blank workflow. 1. Add the **SQL Server** [built-in trigger](/azure/logic-apps/connectors/built-in/reference/sql/#triggers) or [managed trigger](/connectors/sql/#triggers) that you want for your scenario by following the [general steps to add a trigger](../logic-apps/create-workflow-with-trigger-or-action.md?tabs=standard#add-trigger). For example, you might select the built-in trigger named **When a row is inserted** or the managed trigger named **When a row is created**. This example continues with the built-in trigger named **When a row is inserted**. 1. If prompted, provide the [information for your connection](#create-connection). When you're done, select **Create**. 1. After the trigger information box appears, provide the information required by your selected [built-in trigger](/azure/logic-apps/connectors/built-in/reference/sql/#triggers) or [managed trigger](/connectors/sql/#triggers). For this example, in the trigger named **When a row is inserted**, from the **Table name** list, select the table that you want to use. :::image type="content" source="media/connectors-create-api-sqlazure/when-row-inserted-standard.png" alt-text="Screenshot shows Standard workflow designer and built-in action named When a row is inserted."::: 1. Add any other available parameters that you want from the **Advanced parameters** list. In this example, the **When a row is inserted** built-in trigger returns the row that you inserted in the selected table, and nothing else. To perform other tasks, continue by adding either another SQL Server action or another action that performs the next task that you want in your logic app workflow. For example, to view the data in this row, you can add other actions that create a file that includes the fields from the returned row, and then send email alerts. To learn about other available actions for this connector, see the [SQL Server built-in connector reference](/azure/logic-apps/connectors/built-in/reference/sql/#actions) or the [SQL Server managed connector reference](/connectors/sql/#actions). 1. When you're done, save your workflow. On the designer toolbar, select **Save**. --- When you save your workflow, this step automatically publishes your updates to your deployed logic app, which is live in Azure. With only a trigger, your workflow just checks the SQL database based on your specified schedule. You have to [add an action](#add-sql-action) that responds to the trigger. <a name="add-sql-action"></a> ## Add a SQL Server action The following steps use the Azure portal, but with the appropriate Azure Logic Apps extension, you can also use the following tools to build logic app workflows: * Consumption workflows: [Visual Studio Code](../logic-apps/quickstart-create-logic-apps-visual-studio-code.md) * Standard workflows: [Visual Studio Code](../logic-apps/create-standard-workflows-visual-studio-code.md) In this example, the logic app workflow starts with the [Recurrence trigger](../connectors/connectors-native-recurrence.md), and calls an action that gets a row from a SQL database. ### [Consumption](#tab/consumption) 1. In the [Azure portal](https://portal.azure.com), open your Consumption logic app resource. 1. On the resource sidebar menu, under **Development Tools**, select the designer to open your workflow. 1. Add the [**SQL Server** managed action](/connectors/sql/#actions) that you want by following the [general steps to add an action](../logic-apps/create-workflow-with-trigger-or-action.md?tabs=consumption#add-action). This example continues with the **SQL Server** action named **Get row**, which gets a single record. 1. If prompted, provide the [information for your connection](#create-connection). When you're done, select **Create**. 1. After the action information box appears, from the **Table name** list, select the table that you want to use. In the **Row id** property, enter the ID for the record that you want. For this example, the table name is **SalesLT.Customer**. :::image type="content" source="media/connectors-create-api-sqlazure/specify-table-row-id-consumption.png" alt-text="Screenshot shows Consumption workflow designer and action named Get row with the example table name and empty row ID."::: This action returns only one row from the selected table, and nothing else. To view the data in this row, add other actions. For example, such actions might create a file, include the fields from the returned row, and store the file in a cloud storage account. To learn about other available actions for this connector, see the [connector's reference page](/connectors/sql/). 1. When you're done, save your workflow. On the designer toolbar, select **Save**. ### [Standard](#tab/standard) 1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource. 1. On the resource sidebar menu, under **Workflows**, select **Workflows**, and then select the designer to open your workflow. 1. Add the **SQL Server** [built-in action](/azure/logic-apps/connectors/built-in/reference/sql/#actions) or [managed action](/connectors/sql/#actions) that you want for your scenario by following the [general steps to add an action](../logic-apps/create-workflow-with-trigger-or-action.md?tabs=standard#add-action). For example, you might select the built-in action named **Execute query** or the managed action named **Get row**, which gets a single record. This example continues with the managed action named **Get row**. 1. If prompted, provide the [information for your connection](#create-connection). When you're done, select **Create**. 1. After the action information box appears, provide the values for the SQL server name and database name, if you didn't previously provide them. Otherwise, from the **Table name** list, select the table that you want to use. In the **Row id** property, enter the ID for the record that you want. For this example, the table name is **SalesLT.Customer**. :::image type="content" source="media/connectors-create-api-sqlazure/specify-table-row-id-standard.png" alt-text="Screenshot shows Standard workflow designer and managed action named Get row with example table name and empty row ID." lightbox="media/connectors-create-api-sqlazure/specify-table-row-id-standard.png"::: This action returns only one row from the selected table, and nothing else. To view the data in this row, add other actions. For example, such actions might create a file, include the fields from the returned row, and store the file in a cloud storage account. To learn about other available actions for this connector, review the [managed connector's reference page](/connectors/sql/). 1. When you're done, save your workflow. On the designer toolbar, select **Save**. --- <a name="create-connection"></a> ## Connect to your database [!INCLUDE [Create connection general intro](../../includes/connectors-create-connection-general-intro.md)] After you provide this information, continue with the following steps based on your target database: * [Connect to cloud-based Azure SQL Database or SQL Managed Instance](#connect-azure-sql-db) * [Connect to on-premises SQL Server](#connect-sql-server) <a name="connect-azure-sql-db"></a> ### Connect to Azure SQL Database or SQL Managed Instance To access a SQL Managed Instance without using the on-premises data gateway, you have to [configure public endpoints in Azure SQL Managed Instance](/azure/azure-sql/managed-instance/public-endpoint-configure). The public endpoint uses port *3342*, so make sure that you specify this port number when you create the connection from your logic app. In the connection information box, complete the following steps: 1. For **Connection name**, provide a name to use for your connection. 1. For **Authentication type**, select the authentication that's required and enabled on your database in Azure SQL Database or SQL Managed Instance: | Authentication | Description | |----------------|-------------| | **Connection string** | Supported only in Standard workflows with the SQL Server built-in connector. <br><br>Requires the connection string to your SQL server and database. | | **Active Directory OAuth** | Supported only in Standard workflows with the SQL Server built-in connector. For more information, see the following documentation: <br><br>- [Authentication for SQL Server connector](/connectors/sql/#authentication) <br>- [Enable OAuth 2.0 with Microsoft Entra ID](../logic-apps/logic-apps-securing-a-logic-app.md#enable-oauth) | | **Logic Apps Managed Identity** | Supported with the SQL Server managed connector. In Standard workflows, this authentication type is available for the SQL Server built-in connector, but the option is named **Managed identity** instead. <br><br>Requires the following items: <br><br>- A valid managed identity that's [enabled on your logic app resource](../logic-apps/authenticate-with-managed-identity.md) and has access to your database. <br><br>- **SQL DB Contributor** role access to the SQL Server resource <br><br>--- **Contributor** access to the resource group that includes the SQL Server resource. <br><br>For more information, see the following documentation: <br><br>- [Managed identity authentication for SQL Server connector](/connectors/sql/#managed-identity-authentication) <br>- [Server-Level Roles](/sql/relational-databases/security/authentication-access/server-level-roles) | | **Service principal (Microsoft Entra application)** | Supported with the SQL Server managed connector. <br><br>Requires a Microsoft Entra application and service principal. For more information, see [Create a Microsoft Entra application and service principal that can access resources using the Azure portal](../active-directory/develop/howto-create-service-principal-portal.md). | | [**Microsoft Entra integrated**](/azure/azure-sql/database/authentication-aad-overview) | Supported with the SQL Server managed connector. <br><br>Requires a valid managed identity in Microsoft Entra that's [enabled on your logic app resource](../logic-apps/authenticate-with-managed-identity.md) and has access to your database. For more information, see these articles: <br><br>- [Azure SQL Security Overview - Authentication](/azure/azure-sql/database/security-overview#authentication) <br>- [Authorize database access to Azure SQL - Authentication and authorization](/azure/azure-sql/database/logins-create-manage#authentication-and-authorization) <br>- [Microsoft Entra authentication for Azure SQL](/azure/azure-sql/database/authentication-aad-overview) | | [**SQL Server Authentication**](/sql/relational-databases/security/choose-an-authentication-mode#connecting-through-sql-server-authentication) | Supported with the SQL Server managed connector. <br><br>Requires the following items: <br><br>- A data gateway resource that's previously created in Azure for your connection, regardless whether your logic app is in multitenant Azure Logic Apps. <br><br>- A valid user name and strong password that are created and stored in your SQL Server database. For more information, see the following articles: <br><br>- [Azure SQL Security Overview - Authentication](/azure/azure-sql/database/security-overview#authentication) <br>- [Authorize database access to Azure SQL - Authentication and authorization](/azure/azure-sql/database/logins-create-manage#authentication-and-authorization) | The following example shows how the connection information box might appear if you use the SQL Server *managed* connector and select **Microsoft Entra integrated** authentication: :::image type="content" source="media/connectors-create-api-sqlazure/select-azure-ad-sql-cloud-standard.png" alt-text="Screenshot shows SQL Server cloud connection information with selected authentication type."::: 1. After you select **Microsoft Entra integrated**, select **Sign in**. Based on whether you use Azure SQL Database or SQL Managed Instance, select your user credentials for authentication. 1. Select these values for your database: | Property | Required | Description | |----------|----------|-------------| | **Server name** | Yes | The address for your SQL server, for example, *Fabrikam-Azure-SQL.database.windows.net* | | **Database name** | Yes | The name for your SQL database, for example, *Fabrikam-Azure-SQL-DB* | | **Table name** | Yes | The table that you want to use, for example, *SalesLT.Customer* | > [!TIP] > > To provide your database and table information, you have these options: > > * Find this information in your database's connection string. For example, in the Azure portal, find and open your database. On the database menu, select either **Connection strings** or **Properties**, where you can find the following string: > > `Server=tcp:{your-server-address}.database.windows.net,1433;Initial Catalog={your-database-name};Persist Security Info=False;User ID={your-user-name};Password={your-password};MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;` > > * By default, tables in system databases are filtered out, so they might not automatically appear when you select a system database. As an alternative, you can manually enter the table name after you select **Enter custom value** from the database list. This database information box looks similar to the following example: :::image type="content" source="media/connectors-create-api-sqlazure/azure-sql-database-information-standard.png" alt-text="Screenshot shows SQL cloud database information with sample values." lightbox="media/connectors-create-api-sqlazure/azure-sql-database-information-standard.png"::: 1. Now, continue with the steps that you haven't completed yet in either [Add a SQL trigger](#add-sql-trigger) or [Add a SQL action](#add-sql-action). <a name="connect-sql-server"></a> ### Connect to on-premises SQL Server In the connection information box, complete the following steps: 1. For connections to your on-premises SQL server that require the on-premises data gateway, make sure that you've [completed these prerequisites](#multitenant-or-ise). Otherwise, your data gateway resource doesn't appear in the **Connection Gateway** list when you create your connection. 1. For **Authentication Type**, select the authentication that's required and enabled on your SQL Server: | Authentication | Description | |----------------|-------------| | [**SQL Server Authentication**](/sql/relational-databases/security/choose-an-authentication-mode#connecting-through-sql-server-authentication) | Supported with the SQL Server managed connector and SQL Server built-in connector. <br><br>Requires the following items: <br><br>- A data gateway resource that's previously created in Azure for your connection, regardless whether your logic app is in multitenant Azure Logic Apps. <br><br>- A valid user name and strong password that are created and stored in your SQL Server. <br><br>For more information, see [SQL Server Authentication](/sql/relational-databases/security/choose-an-authentication-mode#connecting-through-sql-server-authentication). | | [**Windows Authentication**](/sql/relational-databases/security/choose-an-authentication-mode#connecting-through-windows-authentication) | Supported with the SQL Server managed connector. <br><br>Requires the following items: <br><br>- A data gateway resource that's previously created in Azure for your connection, regardless whether your logic app is in multitenant Azure Logic Apps. <br><br>- A valid Windows user name and password to confirm your identity through your Windows account. <br><br>For more information, see [Windows Authentication](/sql/relational-databases/security/choose-an-authentication-mode#connecting-through-windows-authentication). | 1. Select or provide the following values for your SQL database: | Property | Required | Description | |----------|----------|-------------| | **SQL server name** | Yes | The address for your SQL server, for example, *Fabrikam-Azure-SQL.database.windows.net* | | **SQL database name** | Yes | The name for your SQL Server database, for example, *Fabrikam-Azure-SQL-DB* | | **Username** | Yes | Your user name for the SQL server and database | | **Password** | Yes | Your password for the SQL server and database | | **Subscription** | Yes, for Windows authentication | The Azure subscription for the data gateway resource that you previously created in Azure | | **Connection Gateway** | Yes, for Windows authentication | The name for the data gateway resource that you previously created in Azure <br><br>**Tip**: If your gateway doesn't appear in the list, check that you correctly [set up your gateway](../logic-apps/connect-on-premises-data-sources.md#create-azure-gateway-resource). | > [!TIP] > You can find this information in your database's connection string: > > * `Server={your-server-address}` > * `Database={your-database-name}` > * `User ID={your-user-name}` > * `Password={your-password}` The following example shows how the connection information box might appear if you select **Windows** authentication. :::image type="content" source="media/connectors-create-api-sqlazure/select-windows-authentication-standard.png" alt-text="Screenshot shows SQL Server on-premises connection information with selected authentication." lightbox="media/connectors-create-api-sqlazure/select-windows-authentication-standard.png"::: 1. When you're ready, select **Create**. 1. Continue with the steps that you haven't completed yet in either [Add a SQL trigger](#add-sql-trigger) or [Add a SQL action](#add-sql-action). <a name="handle-bulk-data"></a> ## Handle bulk data Sometimes, you work with result sets so large that the connector doesn't return all the results at the same time. Or, you want better control over the size and structure for your result sets. The following list includes some ways that you can handle such large result sets: * To help you manage results as smaller sets, turn on *pagination*. For more information, see [Get more data, items, or records by using pagination in Azure Logic Apps](../logic-apps/logic-apps-exceed-default-page-size-with-pagination.md). For more information, see [SQL Pagination for bulk data transfer with Logic Apps](https://social.technet.microsoft.com/wiki/contents/articles/40060.sql-pagination-for-bulk-data-transfer-with-logic-apps.aspx). * Create a [*stored procedure*](/sql/relational-databases/stored-procedures/stored-procedures-database-engine) that organizes the results the way that you want. The SQL Server connector provides many backend features that you can access by using Azure Logic Apps so that you can more easily automate business tasks that work with SQL database tables. When a SQL action gets or inserts multiple rows, your logic app workflow can iterate through these rows by using an [*until loop*](../logic-apps/logic-apps-control-flow-loops.md#until-loop) within these [limits](../logic-apps/logic-apps-limits-and-config.md). However, when your logic app has to work with record sets so large, for example, thousands or millions of rows, that you want to minimize the costs resulting from calls to the database. To organize the results in the way that you want, you can create a stored procedure that runs in your SQL instance and uses the `SELECT - ORDER BY` statement. This solution gives you more control over the size and structure of your results. Your logic app calls the stored procedure by using the SQL Server connector's **Execute stored procedure** action. For more information, see [SELECT - ORDER BY Clause](/sql/t-sql/queries/select-order-by-clause-transact-sql). > [!NOTE] > > The SQL Server connector has a stored procedure timeout limit that's [less than 2 minutes](/connectors/sql/#known-issues-and-limitations). > Some stored procedures might take longer than this limit to complete, causing a `504 Timeout` error. You can work around this problem > by using a SQL completion trigger, native SQL pass-through query, a state table, and server-side jobs. > > For this task, you can use the [Azure Elastic Job Agent](/azure/azure-sql/database/elastic-jobs-overview) > for [Azure SQL Database](/azure/azure-sql/database/sql-database-paas-overview). For > [SQL Server on premises](/sql/sql-server/sql-server-technical-documentation) > and [SQL Managed Instance](/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview), > you can use the [SQL Server Agent](/sql/ssms/agent/sql-server-agent). To learn more, see > [Handle long-running stored procedure timeouts in the SQL Server connector for Azure Logic Apps](../logic-apps/handle-long-running-stored-procedures-sql-connector.md). ### Handle dynamic bulk data When you call a stored procedure by using the SQL Server connector, the returned output is sometimes dynamic. In this scenario, follow these steps: 1. In the [Azure portal](https://portal.azure.com), open your logic app and workflow in the designer. 1. View the output format by performing a test run. Copy and save your sample output. 1. In the designer, under the action where you call the stored procedure, add the built-in action named [**Parse JSON**](../logic-apps/logic-apps-perform-data-operations.md#parse-json-action). 1. In the **Parse JSON** action, select **Use sample payload to generate schema**. 1. In the **Enter or paste a sample JSON payload** box, paste your sample output, and select **Done**. > [!NOTE] > > If you get an error that Azure Logic Apps can't generate a schema, check that your > sample output's syntax is correctly formatted. If you still can't generate the schema, > in the **Schema** box, manually enter the schema. 1. When you're done, save your workflow. 1. To reference the JSON content properties, follow these steps: 1. Select inside the edit boxes where you want to reference the JSON properties. 1. Select the lightning icon to open the dynamic content list. 1. From the list, in the [**Parse JSON**](../logic-apps/logic-apps-perform-data-operations.md#parse-json-action) section, select the data tokens for the JSON content properties that you want. ## Related content * [Managed connectors for Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors) * [Built-in connectors in Azure Logic Apps](built-in.md)