What is the difference between dtexec and ISServerExec?

Does ISServerExec ultimately use dtexec to run an SSIS package?

Should I expect the same behavior for a package if I run it from the command line using dtexec with the /ISServer switch as I would get running it manually from the Integration Services Catolog folder in SSMS?

• Edited by David Elish (infoco) 19 hours 52 minutes ago

ISserverExec is not intended for direct use. It is an internal "runner" of packages in SSISDB (catalog).

DtExec is the API for running packages via command line, BAT files, scripts or programmatically /ISServer switch makes sense to use for SSIS 2012 packages and onward deployed to the Catalog.

In SSMS you do not have a way of using either of the above, SSMS runs internal calls to start packages.

I suggest you learn SSIS 1st.

I don't understand your comment about learning SSIS 1st. What was the intention there?

If you question "Should I expect the same behavior for a package if I run it from the command line using dtexec with the /ISServer switch as I would get running it manually from the Integration Services Catolog folder in SSMS" I suspect you are new to SSIS

I'm still not clear on what your intention was? As a moderator do you find it productive and inviting to insult people that post questions? You've accomplished nothing with your comment other than make yourself seem condescending and rude. If we all knew everything there would be no purpose for these forums. 

Thank you very little.

• Edited by David Elish (infoco) 3 hours 30 minutes ago

If I insulted you I apologize, but I feel you drained my time because you could run a test verifying what you need before asking.

As a moderator my goal is to focus on efficiency, make SSIS developers self proficient and at least try to make them think and not Googling answers.

Hi David,

In SSIS 2008 DtExec is a command line utility and by using this we can call/Execute the packages, But SSIS 2012 comes with New SSIS Catalog and the SSIS packages are launched by DtExec but executed by CLR Procedure and this CLR proc Invokes "ISserverexec" which cannot be used as command line i believe . for your reference this Exe located at "C:\Program Files\Microsoft SQL Server\110\DTS\Binn\ISServerExec.exe

Hope this helps!!

Don't forget to mark helpful posts, and answers. It helps others to find relevant posts to the same question.