You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/connectors/connectors-create-api-sqlazure.md
+18-16Lines changed: 18 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: logic-apps
5
5
ms.suite: integration
6
6
ms.reviewer: estfan, azla
7
7
ms.topic: how-to
8
-
ms.date: 10/31/2022
8
+
ms.date: 03/14/2023
9
9
tags: connectors
10
10
## As a developer, I want to access my SQL database from my logic app workflow.
11
11
---
@@ -39,7 +39,7 @@ The SQL Server connector has different versions, based on [logic app type and ho
39
39
|-----------|-------------|-------------------|
40
40
|**Consumption**| Multi-tenant Azure Logic Apps | Managed connector, which appears in the designer under the **Standard** label. 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)|
41
41
|**Consumption**| Integration service environment (ISE) | Managed connector, which appears in the designer under the **Standard** label, and the ISE version, which has different message limits than the Standard class. For more information, review the following documentation: <br><br>- [SQL Server managed connector reference](/connectors/sql) <br>- [ISE message limits](../logic-apps/logic-apps-limits-and-config.md#message-size-limits) <br>- [Managed connectors in Azure Logic Apps](managed.md)|
42
-
|**Standard**| Single-tenant Azure Logic Apps and App Service Environment v3 (Windows plans only) | Managed connector, which appears in the designer under the **Azure** label, and built-in connector, which appears in the designer under the **Built-in** label and is [service provider based](../logic-apps/custom-connector-overview.md#service-provider-interface-implementation). The built-in version differs in the following ways: <br><br>- The built-in version doesn't have triggers. You can use the SQL managed connector trigger or a different trigger. <br><br>- The built-in version can connect directly to an SQL database and access Azure virtual networks. You don't need 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)|
42
+
|**Standard**| Single-tenant Azure Logic Apps and App Service Environment v3 (Windows plans only) | Managed connector, which appears in the designer under the **Azure** label, and built-in connector, which appears in the designer under the **Built-in** label and is [service provider based](../logic-apps/custom-connector-overview.md#service-provider-interface-implementation). The built-in version differs in the following ways: <br><br>- The built-in version can connect directly to an SQL database and access Azure virtual networks. You don't need 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)|
43
43
44
44
### Limitations
45
45
@@ -134,33 +134,35 @@ The following steps use the Azure portal, but with the appropriate Azure Logic A
134
134
135
135
### [Standard](#tab/standard)
136
136
137
-
In Standard logic app workflows, only the SQL Server managed connector has triggers. The SQL Server built-in connector doesn't have any triggers.
138
-
139
137
1. In the [Azure portal](https://portal.azure.com), open your blank logic app workflow in the designer.
140
138
141
-
1. Find and select the [SQL Server trigger](/connectors/sql) that you want to use.
139
+
1. Find and select the SQL Server trigger that you want.
142
140
143
141
1. On the designer, select **Choose an operation**.
144
142
145
-
1. Under the **Choose an operation** search box, select **Azure**.
143
+
1. Under the **Choose an operation** search box, select either of the following options:
144
+
145
+
***Built-in** to view the [SQL Server built-in connector triggers](/azure/logic-apps/connectors/built-in/reference/sql/#triggers)
146
+
147
+
***Azure** to view the [SQL Server managed connector triggers](/connectors/sql/#triggers)
148
+
149
+
This example continues with the SQL Server built-in connector.
146
150
147
151
1. In the search box, enter **sql server**.
148
152
149
153
1. From the triggers list, select the SQL trigger that you want.
150
154
151
-
This example continues with the trigger named **When an item is created**.
152
-
153
-

155
+
This example continues with the trigger named **When a row is inserted**.
154
156
155
157
1. Provide the [information for your connection](#create-connection). When you're done, select **Create**.
156
158
157
159
1. After the trigger information box appears, specify the interval and frequency for how often the trigger checks the table.
158
160
159
161
1. To add other properties available for this trigger, open the **Add new parameter** list and select those properties.
160
162
161
-
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.
163
+
This 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.
162
164
163
-
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/).
165
+
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/#triggers) or the [SQL Server managed connector reference](/connectors/sql/).
164
166
165
167
1. When you're done, save your workflow. On the designer toolbar, select **Save**.
166
168
@@ -226,25 +228,25 @@ In this example, the logic app workflow starts with the [Recurrence trigger](../
226
228
227
229
1. Under the **Choose an operation** search box, select either of the following options:
228
230
229
-
***Built-in**when you want to use SQL Server [built-in actions](/azure/logic-apps/connectors/built-in/reference/sql/) such as **Execute query**
231
+
***Built-in** to view the [SQL Server built-in connector actions](/azure/logic-apps/connectors/built-in/reference/sql/#actions) such as **Execute query**
230
232
231
233

232
234
233
-
***Azure**when you want to use [SQL Server managed connector actions](/connectors/sql) such as **Get row**
235
+
***Azure** to view the [SQL Server managed connector actions](/connectors/sql/#actions) such as **Get row**
234
236
235
237

236
238
237
239
1. In the search box, enter **sql server**.
238
240
239
241
1. From the actions list, select the SQL Server action that you want.
This example selects the built-in action named **Execute query**.
244
246
245
247

0 commit comments