8 Replies Latest reply on Aug 30, 2019 7:08 AM by Bhanu Prakash Badiginchala

    CTRL-M ISSUE CALLING SSIS PACKAGE FROM A STORED PROCEDURE IN SQL

    Ralph Romeo
      Share This:

      The process we use is failing to execute an SSIS package. Instead of running the SSIS package by catalog, our process executes the SSIS package by stored procedure. We do this so we can pass the parameters dynamically.

      So the profile would go:

       

      Control-M -> Stored Procedure -> .dtsx file(SSIS)

       

      I believe the hang up is in Control-M not allowing the stored procedure to direct the connection profile to the .dtsx file for execution.

      We can see the .dtsx file in the SSIS catalog, we can see the stored procedure in the list of stored procedures available.

      We can also execute other SSIS packages/Stored procedures just fine under this connection profile. It’s only this specific tasks that calls a stored procedure that then calls an SSIS package.

       

      We had our DBA run the process locally in SSMS under the connection profile and was successful. So we know that it is Control-M keeping the connection profile from being able to execute the SSIS.

       

      Can anyone tell me what we are possibly missing here?