![]() ![]() If you don't need the inputs and outputs, or if you're already writing the results to a table in the stored procedure, you can simplify this approach. You can store the inputs and outputs in a state table that you can then interact with through your logic app. WAITFOR DELAY than directly call the stored procedure, you can asynchronously run the procedure in the background by using a job agent. If you run this stored procedure from a logic app by using the SQL connector, you get an HTTP 504 Gateway Timeout error as the result. For SQL Server on premises and Azure SQL Managed Instance, you can use the SQL Server Agent.įor example, suppose that you have the following long-running stored procedure, which takes longer than the timeout limit to finish running. For this task, you can use the Azure Elastic Job Agent for Azure SQL Database. Although the SQL connector doesn't natively support an asynchronous mode, you can work around this problem and simulate this mode by using a SQL completion trigger, native SQL pass-through query, a state table, and server-side jobs. Due to the timeout limit, calling these procedures from Azure Logic Apps might create problems. Sometimes these long-running processes are coded as stored procedures explicitly for this purpose. Some stored procedures might take longer than this limit to complete, causing a 504 Timeout error. The SQL connector has a stored procedure timeout limit that's less than 2-minutes. Timeout limit on stored procedure execution For more information, see Handle bulk data using the SQL connector. However, when your logic app has to work with thousands or millions of rows, you want to minimize the costs resulting from calls to the database. ![]() The SQL 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.įor example, when getting or inserting multiple rows, your logic app can iterate through these rows by using an Until loop within these limits. When your logic app works with result sets so large that the SQL connector doesn't return all the results at the same time, or if you want more control over the size and structure for your result sets, you can create a stored procedure that organizes the results the way that you want. Applies to: Azure Logic Apps (Consumption) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |