There is a job running from last five years and it is to took 3 to 4 hrs.
But from last couple of days it is running beyond 24 hrs and it is never stopping. And from the code prespective no changes took place.
I am looking at database prespective that any thing went wrong and making the jobs running forever. like unable to close the database..etc
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
My first guess (without any background info) is that either there has been a problem in the code that has finally been "met" or more likely, the data content has changed so that some unexpected condition has been reached.
If you have statistics on how many rows are in the tables used by this process and can see a big increase recently, this may be causing the longer run times.
In some test environment, can you load the data from last week and see if that runs quickly or if that also now runs longer?