Running a .net console app from my SSIS ETL in Azure SQL Managed instance

[JerryMungo]

.

 

[PsyWulf]

We're doing a lift and shift of a project from an on-premise / VPS environment where the first step of an SSIS ETL runs a console app as a process task in the ETL:

View attachment 886322

What's the best way to execute the .net console app after the lift-and-shift to Azure? We're running a SQL managed instance and data factory for the SSIS execution. Any suggestions very welcome!

Not sure how well a "console" app might function,have you looked into function apps?

 

[HibiscusTunes]

You could repackage package the app as an azure function app? Choose the hosting tier that supports the time you expect the job to run.
Run it in a container?

 

[HibiscusTunes]

@PsyWulf beat me to it

 

[skimread]

Are you using Azure Data Factory for the SSIS steps? Then setup a custom activity.

 

[Spacerat]

Use a script task and then process.execute

 

[Spacerat]

Do you mean a process task? What do I pass through to it for the executable? Locally I refer to the .exe using a Windows drive letter assignment or UNC path: c:\myexecutable.exe or \\server\share\myexecutable.exe... How is that done in Azure - I assume I can stick the exe in a blob container, but how do I refer to it from the SSIS package?

Hmm in Azure, it depends on where you host everything. You may well not be able to access the EXE from where SSIS is hosted. But if you have, you use a scripts task in the SSIS control flow. Then in the code you use Process class with full path to the exe

Process Class (System.Diagnostics)

Provides access to local and remote processes and enables you to start and stop local system processes.

docs.microsoft.com