Sign in
 
HomeLibraryLearnDownloadsTroubleshootingCommunityForums
SQL Server Developer Center >
> 
> 
Confusion about multi-package SSIS 2008 Solution.

Answered Confusion about multi-package SSIS 2008 Solution.

  • Monday, April 16, 2012 3:12 AM
     
     
    Sign In to Vote
    0

    I created two standalone Projects, each in their own separate folders on the file system. I need to call the dtsx packages in each project from a "Main" SSIS program.

    What is the difference between creating a new Main Project and "Adding Existing Packages" to it vs creating a Main Project  and adding New Projects to it? (in the latter case I would not need to have created them Projects in separate directories.)

    TIA,

    Barkingdog



     

All Replies

  • Monday, April 16, 2012 3:47 AM
     
     
    Sign In to Vote
    0

    In SSIS 2008 and 2008 R2 you can consider project as a simple container of packages (like a directory).

    So it depends, how many projects and directories you wish to manage.

    It is changed in SQL Server 2012, where you have project level parameters and connections.

     
  • Monday, April 16, 2012 3:53 AM
     
     
    Sign In to Vote
    0

    "Adding Existing Packages" will copy the packages from the separate folders into the current projects folder.  Adding a new project will create a project folder underneath the current solutions folder. 

    Best Wishes, The Redman; If something helps, please help show it by voting, if it solves, bonus!

     
  • Monday, April 16, 2012 3:59 AM
     
     
    Sign In to Vote
    0

    GGoldspink,

    Your description is exactly what I found.  I'm still not sure of the proc\cons of either approach or maybe they are, in practice, equivalent.

    (under sql 2008)

    Barkingdog


     
  • Monday, April 16, 2012 4:55 AM
     
     Answered
    Sign In to Vote
    0

    Ah, I think I understand the question more now.

    The difference between having 1 project with all packages, as opposed to multiple projects within a solution?

    Piotr Palka has it right.  Wtih grouping you can have things like source code control, particularily with SSIS 2008 and below, where you really only want one dev on a package at a time.  With perhaps 20 or so packages in the works having that broken into 4 projects dealing with various areas may be better, where a dev essentially is assigned to a project. 

    Best Wishes, The Redman; If something helps, please help show it by voting, if it solves, bonus!

     
  • Monday, April 16, 2012 1:24 PM
     
     
    Sign In to Vote
    0

    My experiance with Projects in SSIS , is mainly to orgenize my work and my packages

    ie. i have a group of packages that are Password protected and i have them in Proj1, and a group of packages that the customer can tweak in another proj

    Sincerely SH -- MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).