Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm wondering if there is any difference in performance of a SSIS package if it runs using SQL Server job, vs running using DTEXECUI.EXE Utility or running in BIDS?

Also if the target database in on the server but package is running on a local machine, would it be using the memory on the server or the local machine?

Thanks in advance.

Cheers, Nazila

share|improve this question
up vote 2 down vote accepted

Performance should be the same between running it as a job, via DTEXEC or BIDS.

If the package is run on the SQL Server is uses SQL Servers's buffer pool as it queries the data, then SSIS will use it's own memory space to do work.

If the package is run on the client machine it'll use the SQL Server's buffer pool and memory on the client machine.

Running packages on other machines is usually slower, especially if there is a lot of data to move as the data has to be moved over the network.

share|improve this answer
Just to clarify, performance via dtexec (agent or commandline) and dtexecui would be the same. Running inside BIDS/SSDT will be much slower as it has the debug wrapper around it. – billinkc Aug 14 '12 at 12:13
I agree with you billinkc, I can see the difference when run the package in BIDs (debugging mode) vs when run it using dtexec. – Sky Aug 15 '12 at 1:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.