Hello,
I have an SP that transfers data from one DB to another.
As I run the SP with the management studio - it takes about 15min. But when I scheduled it as an SQL agent job it ran all night and never completed.
The difference I noticed was that the % disk time (of the destination DB) was very high (~100) when I used the agent (which never happened when I ran the SP with the studio).
Only when I restart the SQL service, the disk gets back to normal % disk time.
What could be the reason for that?
My server - Windows 2003 R2 SP1 / SQL 2005 SP2
p.s - could it be related to SQL SP2 ? I didn't have this problem with SP1, but then - I had many other changes since.
Hello Haggai,
Is it possible that something else was running and blocking your process.
You need to check what else was running on the system and also need to capture the perfmon to capture the counters for disk, cpu, memory etc.
regards
Jag
|||By the way, could check SQL Server agent log as well for any errors.|||See if this helps.http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx#EFRAEsql
No comments:
Post a Comment