Easy way to document all DTS packages

  • Hi,

    I am working on Recovery documentation of my SQL Server environment and I was wondering if there was an easy way to document all of our DTS packages.  I thought there was a way to somehow generate the sql code for each package in case they need to be recreated? 

    Thanks in advance!

    Isabelle 

    Thanks!
    Bea Isabelle

  • DTS is not SQL.  It is COM+ objects that have methods and properties that are accessible from applications that can call COM.

    You can export the code of a DTS package by saving it to Visual Basic v6 source code.  This is available out of the box.

    Note... this is not a means to "document" your package (i do have a utility to do that), but a way to recreate it if you have the ability to compile VB source code.

    -Mike Gercevich

  • Hi,

    Thanks for the clarification.  What kind of utility do you have to "document" your packages?  I have the ability to compile VB source code and I can try and save it to VB, but is that the best way to try and document what the DTS package does in case we need to recreate it?

    Thanks!

    Isabelle

    Thanks!
    Bea Isabelle

  • I document with comments in the package.  I include a description of what the package does, the job that executes the package if it's scheduled, and a description of any input parameters.  Every time the package is modified, I add a new comment.

    I find it easier to do it this way than to keep documentation separate.

    Greg

     

    Greg

  • Greg, would your commenting be a text annotation on the DTS Designer page? If so, then be aware that if the package is modified programatically then you will lose the text annotations. This is because they are not part of the object model.

     

    --------------------
    Colt 45 - the original point and click interface

  • Hi,

    I see that some of the DTS packages have text annotation describing what the package does, but not all.  I guess there is no standard that our developers follow.  It also would be time consuming to have to open every DTS package and read what it does and note that in my documentation.  So it seems there is no easy way around this.

    Thanks for all the input!

    Isabelle

    Thanks!
    Bea Isabelle

  • Thanks Phill.  I didn't remember that, but our packages are modified manually so I've never had a problem with it.

    Thanks again,

    Greg

    Greg

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply