Job runs 3 times longer
-
Hello All, I have a job which runs for one hour is now running for 3 hours. I looked at the sql server logs, error logs, event viewer for any errors or anything out of ordinary. I could not find anything. Is there a way to know why the is taking longer? thanks!
-
Hello All, I have a job which runs for one hour is now running for 3 hours. I looked at the sql server logs, error logs, event viewer for any errors or anything out of ordinary. I could not find anything. Is there a way to know why the is taking longer? thanks!
Maybe profiller would help?
-
Hello All, I have a job which runs for one hour is now running for 3 hours. I looked at the sql server logs, error logs, event viewer for any errors or anything out of ordinary. I could not find anything. Is there a way to know why the is taking longer? thanks!
Simple guess; there's now more data in you database. If you have a lot of functions in your query, then those will slow it down. If you do lot of character-manipulations, it will slow down. Convert time often, and it will slow down.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
Simple guess; there's now more data in you database. If you have a lot of functions in your query, then those will slow it down. If you do lot of character-manipulations, it will slow down. Convert time often, and it will slow down.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
-
Hello All, I have a job which runs for one hour is now running for 3 hours. I looked at the sql server logs, error logs, event viewer for any errors or anything out of ordinary. I could not find anything. Is there a way to know why the is taking longer? thanks!
I have run across this in stored procedures, one of the more esoteric problems was "parameter sniffing", basically it comes down to moving your input parameter values to local variables.
Create proc ....
@InputID int
as
Declare LocalID int
Set @LocalID = @InputIDAnd use @LocalID int the body of the procedure
Never underestimate the power of human stupidity RAH
-
or your 1Gb connection is now 10Mb....
In Word you can only store 2 bytes. That is why I use Writer.
-
or your 1Gb connection is now 10Mb....
In Word you can only store 2 bytes. That is why I use Writer.
I meant that dropping an index is less likely. Just like a sudden hardware change. Still possible, just less likely.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.