3
votes

In my pipeline, I have a Lookup activity, which outputs it's data to an Azure Function activity.

I'd like to save the result of the Azure Function activity to a SQL Database.

The only activity I can see which writes to a SQL Database (or other Dataset) is the Copy Data activity, but that doesn't seem like it can take the Azure Function activity's output as it's input.

My "ideal solution" would by to have the inverse of the Lookup activity that takes an input from some other activity and sinks it to a dataset.

It seems a little weird to me that there is a generic Lookup activity to read data from a dataset, but no generic "Store" activity to write data to a dataset.

1

1 Answers

3
votes

Based on the supported connectors of copy activity,azure function connector is not supported.You could adopt a workaround that using Azure Blob Storage as temporary space.

Process the data in azure function and output it to Azure Blob Storage.

Configure Azure Blob Storage as source and SQL Database as sink in copy activity.