I've inherited a large number of DTS packages, and I need
to figure out a way to do the following.

1) script some way of looking at all dts packages to
determine the following:
-- how the connections are set up (to be specific who
is the default user?
-- what types of sql statements is the package
submitting to the database?

Is there a way I can find this information in the system
tables, or write a script to export the packages to VB so
I could use perl to scan them for the information I need?
In short I just want to avoid resorting to opening each
DTS package manually and checking each connection and
transformation.

2) I want to start storing the dts packages in structured
storage files and using clearcase to handle version
control. is there a way to read the structured storage
files and delete the old versions. I want to let
clearcase handle the version control and I don't want to
waste the space keeping the old versions in the structured
storage file

In article <07aa01c394cc$48db59c0$a001280a (AT) phx (DOT) gbl>, "kandrews (AT) erac (DOT) com"
<anonymous (AT) discussions (DOT) microsoft.com> writes
You can certainly write some code to load a package and then enumerate
connections or such like, writing out any details you want. There is no
Save As VB option available in the object model, just the designer. You
could however try the old ScriptPkg tool that came with SQL 7.0. This
was the forerunner to the Save As VB that came along in SQL 2000.


The only way to remove old versions from a storage file is to load the
latest version and then save it back to another file, or use the same
filename, but delete the original file in between the load and save.

The Transfer Packages Sample Application may give you a start-

Tools & Tasks
(http://www.sqldts.net/default.aspx?272)
--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

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