HomeSSISDTEXECWays to execute SSIS package

Comments

Ways to execute SSIS package — 15 Comments

  1. I tried to refer configfile using belwo syntax but it did not work.
    DTEXEC.EXE /F “C:PowerBiPackage.dtsx” /Config “C:PackagesPowerBiConfiguration.dtsconfig”

    After lot of research, i came across work around to refer to SSIS configuration file by following below steps.

    1. open your package file(.dtsx) with notepad.
    2. Naviage to section.
    3. Set physical path of your Config file in below shown property.
    D:\SSISTest\myconfig.dtsConfig

  2. I tried to refer configfile using belwo syntax but it did not work.
    DTEXEC.EXE /F “C:PowerBiPackage.dtsx” /Config “C:PackagesPowerBiConfiguration.dtsconfig”

    After lot of research, i came across work around to refer to SSIS configuration file by following below steps.

    1. open your package file(.dtsx) with notepad.
    2. Naviage to <DTS:Configuration> section.
    3. Set physical path of your Config file in below shown property.
    <DTS:Property DTS:Name=”ConfigurationString”&gtD:\SSISTest\myconfig.dtsConfig</DTS:Property>

    • 1. open your package file(.dtsx) with notepad.
      2. Naviage to section.
      3. Set physical path of your Config file in below shown property.
      <DTS:Property DTS:Name=”ConfigurationString”>D:\SSISTest\myconfig.dtsConfig

  3. Do you have instructions on how to set up a remote computer on a network to execute an SSIS package. Do I have to install SSIS on the remote computer?

  4. This…

    Important Tip: Always remember, no matter what options you choose from above list, but underneath DTEXEC.EXE command-line utility will be called by SQL Server Integration Services RunTime in order to execute SSIS package. The default path of DTEXEC.EXE is “C:Program FilesMicrosoft SQL Server110DTSBinn“. This path may be different for you if you are using different version of SQL Server as well as different method of installation.

    I looked everywhere for confirmation of that. That was my suspicion but I wasn’t sure. We are running into memory issues because of the large number of packages we are running and I thought that if we called with another method, it may eliminate the multiple instances of dtexec running and thus reduce memory consumption. However, it appears that no matter what we do we will run dtexec and thus use much memory. I’m not sure what the solution is for this. If anyone happens to have a suggestion that would be great. Peace.

Leave a Reply

Your email address will not be published. Required fields are marked *

HTML tags allowed in your comment: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>