Why does "Add Existing Package" make a copy of the dtsx?

How do we sync up dtsx files with Visual Source Safe best practices

Each team member needs to create .dtsx files and add to the same project.
When we do "Get Latest Version", other team member's dtsx files are obtained (which is good). But, when we do "Add Existing Package" in Business Intelligence Development Studio, it makes a copy of the existing dtsx file (Example, mypackage.dtsx becomes mypackage(1).dtsx ). Is there another way of adding existing .dtsx files  




Answer this question

Why does "Add Existing Package" make a copy of the dtsx?

  • CougarDave

    Yeah, its annoying isn't it On the other hand it can be helpful if you are adding a package from a completely different place because it creates a copy of it in your project folder. I would guess that this is a VS thing. Pros and cons I suppose.

    As a workaround you could try editing the .dtproj file. Erik Veerman explains how: http://solidqualitylearning.com/blogs/erik/archive/2005/08/08/1269.aspx

    -Jamie


  • James_Peters

    I have a scenario now that I do not want to copy packages when either "Add Existing Package" or "Add Existing Item". I have my existing packages at a folder. I want to create a project at a different folder and directly work on the packages when I add them to the project. I do NOT want create a local copies of package files while I "Add existing package"...

    IS THERE ANY WAY TO ACCOMPLISH THIS



  • TerminalReality

    Can any SSIS expert(s) or SSIS guru please answer the question above...

    Or does anyone know if there is any workaround



  • BrentNewbury

    Jamie -

    It does work if you specify the absolute path to a package inside project file i.e., myProject.dtproj) instead of just a package name. But this has to done manually using a notepad editor..



  • Quoyle

     Michael Entin SQLIS wrote:

    Add Existing Package dialog is provided to let you copy packages from other locations (e.g. remote servers) to the project.

    To add a local file, use Add Existing Item menu.

    It is under top level menu Project, also available by right-clicking project node and selecting Add > Existing Item.




    Thanks Michael,

    For me and my colleagues, it was non-intuitive... to think of .dtsx files as "items" instead of "packages". Maybe "Copy Existing Package" is a better name for "Add Existing Package".

    But, I don't want to sound too pedantic... its understandable.

    cheers,
    nitesh.ambastha@csfb.com



  • JonPL

    OK, found a work-around after some digging. There is a good post by Erik to get this work. Here is what Erik suggested and I tried and worked well.

    Here it is.... every SSIS project has a project file (i.e. test.dtproj )

    If there are some packages already there. a section like should be present. <DtsPackage> ..... </DtsPackage>

    Modify the following to

    .<FullPath> c:\anypath\you want to\package1.dtsx</FullPath>

    A little arkward but do not find a better way ...



  • Mike Russo

    Add Existing Package dialog is provided to let you copy packages from other locations (e.g. remote servers) to the project.

    To add a local file, use Add Existing Item menu.

    It is under top level menu Project, also available by right-clicking project node and selecting Add > Existing Item.



  • Ali Chant

    Steve Wang 2006 wrote:

    Can any SSIS expert(s) or SSIS guru please answer the question above...

    Or does anyone know if there is any workaround

    I don't think there's a way. When you include a package in a project then the package is moved into a place relative to the project. I guess that's a bit annoying but I can understand the rationale behind it.

    -Jamie



  • Why does "Add Existing Package" make a copy of the dtsx?