INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!

Talk With Other Members
Be Notified Of Responses
To Your Posts
Keyword Search
One-Click Access To Your
Favorite Forums
Automated Signatures
On Your Posts
Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Tek-Tips LinkedIn^® Group

Join our
LinkedIn^® Group!

Hook up with past and present colleagues and classmates quickly.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site

(Download This Button Today!)

Feedback

"...I have learned more through this forum than I did on a two day course. Thanks to everyone for their help and other postings that I have found useful..."

More...

Geography

Where in the world do Tek-Tips members come from?

Click Here To Find Out!

Tek-Tips Shirts!

Get your
Tek-Tips Forums
SWAG here!

Home > Forums > Programmers > DBMS Packages > Microsoft SQL Server: Integration Services (SSIS) Forum

Random run duration for a SQL job

Read More Threads Like This One

Elaelian (Programmer)

9 May 12 4:50

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 (Programmer)

9 May 12 8:20

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

----------------------------------------
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
----------------------------------------

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Back To Microsoft SQL Server: Integration Services (SSIS)