My IT manager wants me to regularly save all of our DTS packages as Visual
Basic files and regularly check them into SourceSafe as they are changed.

Is there a *programmatic* way to save a SQL 2000 DTS package as a VB file?
I would hate to constantly be having to manually open up packages and saving
them. It would be much more convenient to simply write a script that
automatically does this.

I know that you can programmatically save a package as a structured storage
file using VBScript and the SaveToStorageFile method. But this won't do for
my needs, because you can't do a meaningful DIFF of the files to see what's
changed.

Unfortunately, there does NOT appear to be the equivalent of a
"SaveToVisualBasicFile" method. But surely, someone out there has devised a
workaround to this. Please help.

CadeBryant wrote:
There is no easy hidden method for doing this.

There is a tool that came on the SQL 7 CD in the samples folder called
ScriptPkg. That was a VB 6 application that scripted out packages. If
you get a copy of that you could update it to handle SQL 2000 quite easily.

There are documentation tools around, so maybe get that output for
tracking and comparison.

Products
(http://www.sqldts.com/default.aspx?401)


Working with Local Packages you already have versions, stored in SQL
Server. Easier to back than sourcesafe!

The DTS Compare tool from www.Red-Gate.com will compare packages, and be
much more meaningful than any Diff on code files. They recently updated
it, and very slick and fast it is too. Does a nice comparison as well of
course.



--
Darren
http://www.sqldts.com
http://www.sqlis.com

Thanks, Darren.

I don't have the SQL 7 CD. Is there a place online where I can download
ScriptPkg?

"Darren Green" wrote: