Where the package is stored has no effect on the running of the package.
The SSIS catalog give you centralized logging. Please see:
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello, am using the SQL Server 2014 Import and Export Wizard to import a flat file into a SQL Server table.
At the last option it asks Save SSIS package as SQL Server or File System...which would be faster in running via a SQL Agent job?
The flat file is very large so looking to see if saving & running with SQL Server option would be faster than vs as a File System... which am guess would be slower since it has to do an extra step going out to the Windows OS File System?
Also any other things to consider/concerns/be aware of...like if need to migrate to a newer version to SQL Server 2019 will migrating the saved SSIS package location be easier or harder based on which option to save it as?
Thanks in advance.
Where the package is stored has no effect on the running of the package.
The SSIS catalog give you centralized logging. Please see:
The question "at SQL Server or Filesystem" normally means where to store the SSIS-package in case you want to deploy it.
SSIS has the option to read packages from SQL Server or from Filesystem...
This is not about your flatfile!
Of cause - upgrading from 2014 to 2019 is always a good option (it just runs faster ;-) )
Thanks for the replies.