I am just about to put my first ssis package into production. Not only
is it my first, its the first one where I am working. SSIS gives us
choices about locations in which to store the packages. Would someone
care to discuss the pros and cons of each?

Any "war stories" of your experience are also welcome.

Thanks,
IanO

IanO wrote:
firstly:
source:
http://sqljunkies.com/WebLog/knight_.../05/13523.aspx

my additional notes:

·Storing packages in file system allows accessing to packages even if
SQL Server instance is not active.
·File-based packages can be executed manually through dtexec.exe tool
(only locally!)
·Packages stored in SQL Server can be executed manually through SQL
Server Management Studio console - they can be launched remotely

finally:
http://blogs.conchango.com/jamiethom...1/05/2559.aspx

summary:
seems that file storing is more popular

HTH

Hello IanO,

Kirk haselden has a discussion about this in his book and he also talks about
it on the web in his blog. Personally I have deployed to both and cannot
give a definitive "You should store them here". I have also worked at places
where the only location to which you are permitted to save them is the file
system.

For me there really is no overriding pros and cons.

File System

Easy Deployment
No need for SQL Server (as it should be)


Msdb

apply role security
watched by the SSIS Service
Backed up with the msdb backup.







Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com