January 12, 2007 at 4:00 pm
When I run my SSIS package in Designer, it takes only a few seconds to run. When I schedule it as a SQL job, it runs about 4 minutes. Is there any configuration setting I have to change?
January 15, 2007 at 8:00 am
This was removed by the editor as SPAM
January 15, 2007 at 8:31 am
turn on the logging to see where the hold up is. are you comparing running it at the same times?
January 18, 2007 at 2:22 pm
Thanks for the response. I am not running the package in Designer and job at the same time. I turned on the logging and I don't see any hold up on the events for the package. Below is the job history (in text). It ran for 6:05 minutes.
Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted
01/18/2007 14:37:19,TS_Test,Unknown,0,SAT4DB05,TS_Test,(Job outcome),,The job succeeded. The Job was invoked by User RACKSPACE\leah.peters. The last step to run was step 1 (Run Ticket Search test).,00:06:05,0,0,,,,0
01/18/2007 14:37:19,TS_Test,Unknown,1,SAT4DB05,TS_Test,Run Ticket Search test,,Executed as user: RACKADW2K\sqlsvc1. The package executed successfully. The step succeeded.,00:06:05,0,0,,,,0
The job started at 2:37:19 pm as you can see above but the first event "OnPreValidate" didn't start until 2:42:51 pm below. How do I find out what's happening between those times? The last event ended at 2:43:23 pm.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply