I need to make a decision whether to store a DTS package on the SQL Server
or on the File system.
Can the group please fill in Advantages and Disadvantages on either side.

Thank you all in Advance
~Sat

I would immediately think of

SQL Server

Backed up with your MSDB backup
Centrally stored
Can be queried for versions

File System

Easily distributable
You can store the packages in a hierarchy
Source Control






"Satish Balusa" <sbalusaN0_SpaM (AT) corillian (DOT) com> wrote

Hi Satisch,

"Satish Balusa" <sbalusaN0_SpaM (AT) corillian (DOT) com> schrieb im Newsbeitrag
news:Oun57caVFHA.1384 (AT) TK2MSFTNGP09 (DOT) phx.gbl...
it depends on the usage.
I develop DTS packages in the SQL Server. This allows easier/faster
openening with the list of packages in EM and also easy switching/rollback
to earlier version.
Also the history can be helpful for testing.
Each time I get a stable and tested version I save it as file to add it to
the source control system and deploy it.
When you execute it in production, you normaly store it in the SQL Server
to allow the Admins a fast overview of packages and jobs and maybe the
usage of the package history.
Also the job creation and scheduling is nicely integrated when packages are
stored inside of the SQL Server.
But from the application view you may not want to install packages inside
of the SQL Server, but instead save them as dts files together with the
application and execute them inside of the application.

Helge

In message <ek3bmiaVFHA.3176 (AT) TK2MSFTNGP12 (DOT) phx.gbl>, Allan Mitchell
<allan (AT) no-spam (DOT) sqldts.com> writes
Simple to distribute, as can be done from remote machines with SQL
access only

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org