Post reply

Flat File connection manager at package level in project deployment model

  • August 13, 2015 at 3:53 am

    #303469

    I have an SSIS Project which has few packages .All of the packages involve transferring file data to/from database to flat files. I am confused if I need to have my flat file connection manager for each package at package level or project level. The flat files are not related to each other and our specific to packages only.

    If I make package level parameters and package level flat file connection managers ,I will still be able to configure those as per my environment when I deploy under Integration services catalogue?

    Also considering good project practice, which is a good idea to have flat file connection managers for each package at package level or project level?

    Thanks,

  • August 13, 2015 at 4:07 am

    #1819586

    happy55 (8/13/2015)

    I have an SSIS Project which has few packages .All of the packages involve transferring file data to/from database to flat files. I am confused if I need to have my flat file connection manager for each package at package level or project level. The flat files are not related to each other and our specific to packages only.

    If I make package level parameters and package level flat file connection managers ,I will still be able to configure those as per my environment when I deploy under Integration services catalogue?

    Also considering good project practice, which is a good idea to have flat file connection managers for each package at package level or project level?

    Thanks,

    If they're specific to the package, leave them scoped to the package. You can always expand the scope later, if necessary.

    I will still be able to configure those as per my environment when I deploy under Integration services catalogue?

    Not a problem.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • August 13, 2015 at 6:43 am

    #1819638

    Thanks. The package levels parameters are also configurable in Integration Services catalogue?

    Is it a good practice to save the paths in database tables or make them as package parameters?

  • August 13, 2015 at 7:34 am

    #1819665

    happy55 (8/13/2015)

    Thanks. The package levels parameters are also configurable in Integration Services catalogue?

    Is it a good practice to save the paths in database tables or make them as package parameters?

    Yes to question 1 (I thought I'd already confirmed this).

    Question 2: there's no correct answer to this. I choose to save connection managers in the package or project and use environment variables to force their value and it works well.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

Viewing 4 posts - 1 through 3 (of 3 total)

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