0
We wanted to migrate to SQL Server 2017. After we set up everything, we had a problem with the performance of the server.
After a few weeks, we found out that the SSIS packages requires exact 10 seconds more to run for each package.
This only happens if we run the package with the
dtexec /f
command and load the package from the file system.
We already tried to recreate the package and to run the dtexec with 32-bit and 64-bit. Nothing changed with this. However, if we run the package in Visual Studio or in the integration service catalog the package starts immediately and have a runtime reduced by the 10 seconds.
Are you running dtexec /f without any additional parameter? – Alberto Morillo – 2019-09-27T05:55:56.230
You using /f path only? – Alberto Morillo – 2019-09-27T06:04:58.420