Skip to content

Commit 6d4d8d9

Browse files
authored
Merge pull request #39309 from kubikb/master
Clarify data passed to Azure SQL DB sink stored procedures
2 parents 2549046 + c31a6aa commit 6d4d8d9

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

articles/data-factory/connector-azure-sql-database.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -488,7 +488,7 @@ BEGIN
488488
END
489489
```
490490

491-
**Option 2:** You also can choose to [invoke a stored procedure within the copy activity](#invoke-a-stored-procedure-from-a-sql-sink). This approach runs each row in the source table instead of using bulk insert as the default approach in the copy activity, which isn't appropriate for large-scale upsert.
491+
**Option 2:** You also can choose to [invoke a stored procedure within the copy activity](#invoke-a-stored-procedure-from-a-sql-sink). This approach runs each batch (as governed by the `writeBatchSize` property) in the source table instead of using bulk insert as the default approach in the copy activity.
492492

493493
### Overwrite the entire table
494494

@@ -503,10 +503,7 @@ The steps to write data with custom logic are similar to those described in the
503503

504504
## <a name="invoke-a-stored-procedure-from-a-sql-sink"></a> Invoke a stored procedure from a SQL sink
505505

506-
When you copy data into Azure SQL Database, you also can configure and invoke a user-specified stored procedure with additional parameters. The stored procedure feature takes advantage of [table-valued parameters](https://msdn.microsoft.com/library/bb675163.aspx).
507-
508-
> [!TIP]
509-
> Invoking a stored procedure processes the data row by row instead of by using a bulk operation, which we don't recommend for large-scale copy. Learn more from [Best practice for loading data into Azure SQL Database](#best-practice-for-loading-data-into-azure-sql-database).
506+
When you copy data into Azure SQL Database, you also can configure and invoke a user-specified stored procedure with additional parameters on each batch of the source table. The stored procedure feature takes advantage of [table-valued parameters](https://msdn.microsoft.com/library/bb675163.aspx).
510507

511508
You can use a stored procedure when built-in copy mechanisms don't serve the purpose. An example is when you want to apply extra processing before the final insertion of source data into the destination table. Some extra processing examples are when you want to merge columns, look up additional values, and insert into more than one table.
512509

0 commit comments

Comments
 (0)