Save SSIS package as SQL Server or File System

techresearch7777777 1,981 Reputation points
2022-09-23T17:31:28.727+00:00

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.

SQL Server Other
0 comments No comments
{count} votes

Accepted answer
  1. Tom Phillips 17,771 Reputation points
    2022-09-23T17:59:27.797+00:00

    Where the package is stored has no effect on the running of the package.

    The SSIS catalog give you centralized logging. Please see:

    https://www.mssqltips.com/sqlservertip/2450/ssis-project-deployment-model-in-sql-server-2012-part-1-of-2/

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Bjoern Peters 8,921 Reputation points
    2022-09-23T17:43:41.45+00:00

    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 ;-) )

    0 comments No comments

  2. techresearch7777777 1,981 Reputation points
    2022-09-23T19:05:45.123+00:00

    Thanks for the replies.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.