Random run duration for a SQL job

[Elaelian]

Hi,

I have an issue that I cannot understand anymore...

I have a server A (Windows Server 2003) hosting a database.

I have developed a DTS to save in this database some data for other databases from other servers.

This DTS is runned each morning with MS SQL Server (automatic execution).

I don't understand why every day, the run duration is random. Sometimes, the job spends 15 minutes to be done, sometimes, it spends 30 minutes...

I think that locks can be the issue. I want to trace them with SQL Profiler but the matter is that I want to start tracing at 5am. I'm not at work at that time so how can I make start the trace automatically?

If you don't think that the locks are the problem, do you know please how I can begin me research to solve this problem?

Thans you in advance,

Elaelian

 

[SQLScholar]

Firstly for your trace - start it via cmdline.

Create a batch file using this as a guide:

http://pentonizer.com/sql-server/sql-profiler-command-line-options/

Then schedule it to run using scheduled tasks.

What i would say is issues like this are VERY hard to find. It could be a backup on SQL running late, or even on a seemingly unconnected server (backup running on a different server causing network traffic on a switch\cable to be high - causing a delay).

Dan

----------------------------------------

http://www.fountain.me.uk

Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind - Bernard Baruch

Computer Science is no more about computers than astronomy is about telescopes - EW Dijkstra
----------------------------------------