Hello Team,
We have an SSIS package created including Execute Process Task (which is in control flow task). Execute Process task is placed in for each task. We have a folder in local machine (where SSIS Packages also deployed) where in list of files (files are of different format and are about 50 plus files in count). So, the purpose of Execute Process task is to call each file, parsing data and load it into Azure SQL Database. Since Execute Process task is in For each task, the loop run through as many times as the number of files. In Execute Process task we have used PERL script to call the file, process the data and load into Azure SQL Database.
We have followed the Azure best practices lifting and shift SSIS packages using SSISDB route. Created SHIR to connect to files folder and Perl script, created Catalog database to enable SSISBD to deploy SSIS package, created Azure-SSIS IR for integration joining both SHIR and Azure-SSIS and VNet in the configurations.
Challenge is, SSIS packages run successfully (in 90seconds) in on Prim virtual machine wherein we try to run same package in Integration Runtime (or ADF Pipeline Execute SSIS Package) it is taking forever and not even throwing error (7 hours and more). We check the log files but of no useful information to trace. We are not able recreate the pipeline in ADF so. Any alternative suggestions to identify root cause or to reconfigure is appreciated. Is ADF supports Execute Process Task which is calling PERL script. Are there any options we should check or considered to make this package execute successfully in Azure Data Factory.
Krishna