Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

Command Prompt DTEXEC Vs. Scheduled Job

$
0
0

Hi Gurus,

I have a strange problem going. Any help/direction on this would be appreciated. The issue goes like this:

I have a package which fetches about 10M rows from Oracle (single table, no joins). I have created a Job and scheduled this package to run daily. However, I noticed that it takes about 4 hours for it to finish its work. I couldn't find anything to improve on time taken. While playing around, I ran the same package using dtexec utility from command prompt. To my surprise, the package finished in appx 15-20 minutes (I tried this multiple times. Same.)

So I changed the job to run a Command instead of SSIS Package. But when I do so, it again takes 4 hours.

Do note that the job is using my own windows credentials in form of proxy. I have already tried the 32 bit option. Playing around with buffers etc. No matter what I do, the results wont change.

Any Idea on what would make my package run faster via a scheduled job??

Thanks in advance.


Let me know if you have any more questions on this. Please mark this post as an answer if it helps you resolve your question. - Bhawesh



Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>