Post reply

DTS Job scheduling taking very long.

  • January 26, 2007 at 10:53 am

    #69391

    hi guys could there be a reason why when i run a dts mannually it takes 5 minutes to run and then when it runs as a scheduled job it takes 2 hours? I disabled the other jobs to see if it were too many running at the same time. but it takes the same as long.

  • January 26, 2007 at 11:23 am

    #685915

    A few thoughts:  is the server where you scheduled the job running at high CPU?  Is the server where you scheduled the job not either the source for the data or the target?

    Russel Loski, MCSE Business Intelligence, Data Platform

  • January 29, 2007 at 4:50 am

    #686100

    Are any other processes running on the server that you don't know about?  For example, I once had a problem when there was conflict between IT backups and jobs running on my server.  If they ever clashed, then my jobs slowed down considerably.  Once the clash was sorted out, the jobs started running at warp(ish) speed again.

  • January 29, 2007 at 7:39 am

    #686136

    basically this dts is just copying tables from another database at another server and copying them to my sql server database. It  usually takes about 3 minutes to run.. i checked and there are no other jobs running... the backups are run 3 times a day. I even recreated my odbc conection and the same thing happens. I don't see any errors in my sql server profiler neither. Something else I could check?

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply