I have a process that incorporates something with selection when I try to access it from access or even That takes 4 minutes even in the management studio. Every 40 seconds with the job check if there is that it took about 15 seconds to execute and execute this process.
What could be the problem? Why is the same process executed by the job compared to the process executed with access or query in the management studio 10 times faster?
I doubt there is a difference at any time here. The problem is that after running several times after the job, the data is cached in the memory, and in this way it runs very fast.
You reboot a new one and then check the time for the run, it should be similar to all sources
It is not clear how are you calling this routine , But is it possible that the job is not waiting to complete the schedule?
And any data back to the client application regularly? Perhaps the difference is that when access (or SSMS) is triggered, a lot of data is returned from the stored procedure, but when using a job agent, there is no provision to consume the returned data. , So the return of data is ignored and thus the results (S) run faster.
Comments
Post a Comment