Running SSIS packags: file-based vs database-stored

[Nicolas Verhaeghe]

I was wondering what each of your preference was and why you would
believe this is a good solution?

I like running packages as database-stored, they are less likely to be
modified by an external process or the files to be accidentally
deleted.

What's your take?

[Bob Barrows]

Post by Nicolas Verhaeghe
I was wondering what each of your preference was and why you would
believe this is a good solution?
I like running packages as database-stored, they are less likely to be
modified by an external process or the files to be accidentally
deleted.

I store my deployed packages in the database, so I cannot really answer
your question. However, I did want to reassure you that your question is
getting read.

I develop using the file-based packages, so that source control can be
used (something that is not possible with packages in msdb). To deploy,
I use the "Save copy ..." menu item, specifying the server to which I
deploy the package.

[Nicolas Verhaeghe]

Post by Bob Barrows

Post by Nicolas Verhaeghe
I was wondering what each of your preference was and why you would
believe this is a good solution?
I like running packages as database-stored, they are less likely to be
modified by an external process or the files to be accidentally
deleted.

I store my deployed packages in the database, so I cannot really answer
your question. However, I did want to reassure you that your question is
getting read.
I develop using the file-based packages, so that source control can be
used (something that is not possible with packages in msdb). To deploy,
I use the "Save copy ..." menu item, specifying the server to which I
deploy the package.
--
HTH,
Bob Barrows

This is what I like to do as well. It seems to be that storing the
packages in DB ensures a faster load and prevents from a loss or
corruption of the dtsx file.