Post reply

Best DTS Practise ? Many DTS Packages as 1 job OR 1 DTS workflow with many steps?

  • January 26, 2004 at 9:06 am

    #59599

    Good morning

    I have a weekly download from a HP3000 and currently this is set up with 6 DTS packages combined in 1 job. I need to make quite a few changes and would also like to build in some auditing, and it does look tempting to make 1 DTS package with 6 steps. What are the cons and pros of have all steps in one DTS package ??

    Thanks

    Finn Erik

     

     

  • January 26, 2004 at 7:30 pm

    #491699

    It depends on your data requirements. Do you ALWAYS load ALL six files? If one file fails to load properly should the remaining files still be loaded. Would there ever be a need to load one file, say on an ad-hoc basis?

    If your scenario is that you need to load all six files and always in a certain sequence, and you'll never load a single file by itself, then you can put it all in one package and benefit from having the predefined workflow all in one package.

    Otherwise, you can benefit from having each file loaded in a seperate package. You can also create a "Parent" package that runs all six "child" packages. The parent package could also do tasks like initialising your audit table/file, etc...

    Conversely, having child packages can lead to code duplication, versioning and deployment issues.

     

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

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

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