Multiple Flat files

  • Hello Gurus - I am building a package that has to output 4 flat files. Each flat file uses different tables. What is the best route to take to accomplish this. Would one data flow task, four ole db and four flat file destination be the best route for this?

    Thanks!

  • elee1969 (3/20/2014)


    Hello Gurus - I am building a package that has to output 4 flat files. Each flat file uses different tables. What is the best route to take to accomplish this. Would one data flow task, four ole db and four flat file destination be the best route for this?

    Thanks!

    Four data flows, each containing an OLEDB source and flat-file destination, would work.

    You would then have the option of running in parallel, series, or mixed (eg, two at a time) through appropriate use of Sequence containers.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Phil Parkin (3/20/2014)


    elee1969 (3/20/2014)


    Hello Gurus - I am building a package that has to output 4 flat files. Each flat file uses different tables. What is the best route to take to accomplish this. Would one data flow task, four ole db and four flat file destination be the best route for this?

    Thanks!

    Four data flows, each containing an OLEDB source and flat-file destination, would work.

    You would then have the option of running in parallel, series, or mixed (eg, two at a time) through appropriate use of Sequence containers.

    Thanks Phil for clarifying.

  • Depending on how strict your regression testing is, you might be better off with four separate packages and a master package that calls the four child packages. If you put them all in the same package and change one DFT, then RegTest may make you retest all the streams.

  • aaron.reese (3/21/2014)


    Depending on how strict your regression testing is, you might be better off with four separate packages and a master package that calls the four child packages. If you put them all in the same package and change one DFT, then RegTest may make you retest all the streams.

    If the number of files you need to process is likely to increase in future, that's another good reason for taking this approach - stops your package getting too cumbersome.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Phil Parkin (3/21/2014)


    aaron.reese (3/21/2014)


    Depending on how strict your regression testing is, you might be better off with four separate packages and a master package that calls the four child packages. If you put them all in the same package and change one DFT, then RegTest may make you retest all the streams.

    If the number of files you need to process is likely to increase in future, that's another good reason for taking this approach - stops your package getting too cumbersome.

    This package will never exceed for output files. On a different note could this task be accomplished with a foreach loop container? If so, how would this be setup?

    Thanks Gurus !!

  • If the files have an identical structure and it is only the target name that changes then yes, otherwise you might as well have four DFTs (plus DFTs can operate in parallel, whereas a FEL by definition will not)

  • aaron.reese (3/24/2014)


    If the files have an identical structure and it is only the target name that changes then yes, otherwise you might as well have four DFTs (plus DFTs can operate in parallel, whereas a FEL by definition will not)

    Yes, all four will have different file structure. Thanks for the information.

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

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