Main question is how to connect or map dtsx and dtsconfig file in different computer?

  • I have SSIS package. It pulls the data from production server and dump in devlopment server. It run perfectly. If somebody want to run same package in QA or Prod server, wHERE QA AND pROD server name might change and database name might change. One of the way to solve the problem is make XML cONFIGFILE and dtsx files and send to QA or Prod guys. So, I make its dtsx file and package location "File System" save it at c:\test\text.dtsx. I went to BIDS, make config file, where I choose connectionString of source and destination from where I can know servername, databasename. I save this config file at c:\test\text123.dtsconfig.

    When I send to QA or Prod guys. How they will link these dtsx and dtsconfig file. So that they can open dtsconfig file and modyfy the QA servername or Prod Server name and run ssis package.

    Main question is how to connect or map dtsx and dtsconfig file in different computer?

  • Munabhai (7/18/2012)


    I have SSIS package. It pulls the data from production server and dump in devlopment server. It run perfectly. If somebody want to run same package in QA or Prod server, wHERE QA AND pROD server name might change and database name might change. One of the way to solve the problem is make XML cONFIGFILE and dtsx files and send to QA or Prod guys. So, I make its dtsx file and package location "File System" save it at c:\test\text.dtsx. I went to BIDS, make config file, where I choose connectionString of source and destination from where I can know servername, databasename. I save this config file at c:\test\text123.dtsconfig.

    When I send to QA or Prod guys. How they will link these dtsx and dtsconfig file. So that they can open dtsconfig file and modyfy the QA servername or Prod Server name and run ssis package.

    Main question is how to connect or map dtsx and dtsconfig file in different computer?

    The config file path is stored in the SSIS package so it as already linked that way. If you're allowing the users to simply copy the package from a file share or are emailing it to them or something like that then the dtsConfig file must reside in the same location on all their machines or they must modify the SSIS package XML accordingly to point to the proper location, else the SSIS package will not find it.

    You have the option to deply packages using a manifest file as well, which can be used to solve your issue: SSIS - Creating a Deployment Manifest by Devin Knight

    If your users are executing the packages using DTExec from a command line, alternatively you can do away with the dtsConfig file and setup variables in your SSIS package that the users can provide values for in the command line call to DTExec. In this mode your connection strings would be built dynamically using an Expression containing a reference to a variable name the user supplies. See the /Set option in the DTExec documentation:

    DTExec SSIS 2012

    DTExec SSIS 2008 R2

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • Thank you. If I put both dtsx and dtsconfig file together in different computer then when I execute package it will aumotmatically point the path correct.

  • If you place both the dtsx and dtsConfig files in the same path on all computers, i.e. the one you use for development on your own machine, then yes, the dtsConfig file will be picked up when running on all machines.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • Yes, I got it that part and it does work too. If you know, could you please tell me if location is different then how to point that dtsconfig to dtsx file

  • Munabhai (7/18/2012)


    Yes, I got it that part and it does work too. If you know, could you please tell me if location is different then how to point that dtsconfig to dtsx file

    It's the other way around. A dtsx file points to a dtsConfig file.

    See the link I posted earlier about creating a deployment manifest file. This will allow your users to "install" your dtsx and dtsConfig files and they will be linked during that process per where they choose to place the files.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • Great. Thanks for your help

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

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