execute a single package within SSIS

• dgl

  SSC Veteran

  Points: 229

  More actions

  October 26, 2018 at 6:38 pm

  #380396

  I am using Visual Studio 2013.

  At every company I've worked, we have always had only one package per solution.  I never gave it much thought as I just had to comply.  Now I have a solution with multiple packages.  I've noticed some unexpected behavior.
  When I have a package selected (via the tab) and I am looking at the package components (i.e. Design Mode) and I select "Start", a different package may execute.  As an alternative, I noticed that I can right-click on the package in the Solution Explorer to execute a specific package.  It also seems that this only happens when I first open the solution and run the first package.
  I expected that the package visible in Design Mode would be run
  Please offer guidance.
  Thanks.

• Ells

  SSCrazy Eights

  Points: 9901

  More actions

  October 30, 2018 at 7:20 am

  #2011672

  Dude,
  When you  start a package by  using the  green "play" at the top of Visual Studio it will start the package it is configured to start.
  in Visual Studio

  1. Right click on the Solution folder in the Solution view window
  2. Click on Properties
  3. Click on Configuration Properties
  4. Go To Debugging
  5. Click on Start Action
  6. Set the start object id to Active Package (it may have a defined package as the start package)

  Hope that helps
  M

• dgl

  SSC Veteran

  Points: 229

  More actions

  October 30, 2018 at 7:27 am

  #2011675

  Thank you. 

• dgl

  SSC Veteran

  Points: 229

  More actions

  October 31, 2018 at 9:51 am

  #2011890

  Ells - Tuesday, October 30, 2018 7:20 AM

  Dude,
  When you  start a package by  using the  green "play" at the top of Visual Studio it will start the package it is configured to start.
  in Visual Studio

  1. Right click on the Solution folder in the Solution view window
  2. Click on Properties
  3. Click on Configuration Properties
  4. Go To Debugging
  5. Click on Start Action
  6. Set the start object id to Active Package (it may have a defined package as the start package)

  Hope that helps
  M

  I was finally able to explore this solution.  Surprisingly this setting is already in place.  I have also experimented a bit.  The only time I have this issue is the very first time I execute a package after opening the solution.  After that, whichever package is active gets executed.