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/data-factory/transform-data-using-script.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ You can use the Script activity to invoke a SQL script in one of the following d
22
22
23
23
- Azure SQL Database
24
24
- Azure Synapse Analytics
25
-
- SQL Server Database. If you are using SQL Server, install Self-hosted integration runtime on the same machine that hosts the database or on a separate machine that has access to the database. Self-Hosted integration runtime is a component that connects data sources on-premises/on Azure VM with cloud services in a secure and managed way. See the [Self-hosted integration runtime](create-self-hosted-integration-runtime.md) article for details.
25
+
- SQL Server Database. If you're using SQL Server, install Self-hosted integration runtime on the same machine that hosts the database or on a separate machine that has access to the database. Self-Hosted integration runtime is a component that connects data sources on-premises/on Azure VM with cloud services in a secure and managed way. See the [Self-hosted integration runtime](create-self-hosted-integration-runtime.md) article for details.
26
26
- Oracle
27
27
- Snowflake
28
28
- Azure Database for PostgreSQL
@@ -37,7 +37,7 @@ The script can contain either a single SQL statement or multiple SQL statements
37
37
38
38
## Syntax details
39
39
40
-
Here is the JSON format for defining a Script activity:
40
+
Here's the JSON format for defining a Script activity:
41
41
42
42
```json
43
43
{
@@ -143,7 +143,7 @@ Sample output:
143
143
|Property name |Description |Condition |
144
144
|---------|---------|---------|
145
145
|resultSetCount |The count of result sets returned by the script. |Always |
146
-
|resultSets |The array which contains all the result sets. |Always |
146
+
|resultSets |The array that contains all the result sets. |Always |
147
147
|resultSets.rowCount |Total rows in the result set. |Always |
148
148
|resultSets.rows |The array of rows in the result set. |Always |
149
149
|recordsAffected |The row count of affected rows by the script. |If scriptType is NonQuery |
@@ -154,10 +154,10 @@ Sample output:
154
154
155
155
> [!NOTE]
156
156
> - The output is collected every time a script block is executed. The final output is the merged result of all script block outputs. The output parameter with same name in different script block will get overwritten.
157
-
> - Since the output has size / rows limitation, the output will be truncated in following order: logs -> parameters -> rows. Note, this applies to a single script block, which means the output rows of next script block won’t evict previous logs.
157
+
> - Since the output has size / rows limitation, the output will be truncated in the following order: logs -> parameters -> rows. This applies to a single script block, which means the output rows of next script block won’t evict previous logs.
158
158
> - Any error caused by log won’t fail the activity.
159
-
> - For consuming activity output resultSets in down stream activity please refer to the [Lookup activity result documentation](control-flow-lookup-activity.md#use-the-lookup-activity-result).
160
-
> - Use outputLogs when you are using 'PRINT' statements for logging purpose. If query returns resultSets, it will be available in the activity output and will be limited to 5000 rows/ 4MB size limit.
159
+
> - For consuming activity output resultSets in down stream activity, refer to the [Lookup activity result documentation](control-flow-lookup-activity.md#use-the-lookup-activity-result).
160
+
> - Use outputLogs when you're using 'PRINT' statements for logging purpose. If query returns resultSets, it will be available in the activity output and will be limited to 5000 rows/ 4MB size limit.
0 commit comments