Delay in SQLAgent Service startup

Hi,
On a number of servers we are facing issues regarding the SQL Server Agent
service. The service is experiencing a delay during startup, more than the
wait hint period. THe service should ideally be starting in 30 seconds (Or it
seems to say so in the Wait Hint). But it is taking around 1min. Our software
thinks it is a timeout and raises an error.
Following is the SQLAgent log file of when the service is starting:
2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86
unicode retail build) : Process ID
2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86
unicode retail build) : Process ID 1956
2006-11-08 03:30:10 - ? [101] SQL Server [MACHINE_NAME]\[INSTANCE] version
8.00.760 (0 connection limit)
2006-11-08 03:30:10 - ? [102] SQL Server ODBC driver version 3.81.9031
2006-11-08 03:30:10 - ? [103] NetLib being used by driver is DBMSLPCN.DLL;
Local host server is [MACHINE_NAME]\[INSTANCE]
2006-11-08 03:30:10 - ? [310] 2 processor(s) and 1023 MB RAM detected
2006-11-08 03:30:10 - ? [339] Local computer is [MACHINE_NAME] running
Windows NT 5.0 (2195) Service Pack 3
2006-11-08 03:30:10 - ? [124] Subsystem 'TSQL' successfully loaded (maximum
concurrency: 20)
2006-11-08 03:30:40 - ? [124] Subsystem 'CmdExec' successfully loaded
(maximum concurrency: 10)
2006-11-08 03:30:40 - ? [124] Subsystem 'Snapshot' successfully loaded
(maximum concurrency: 100)
2006-11-08 03:30:40 - ? [124] Subsystem 'Distribution' successfully loaded
(maximum concurrency: 100)
2006-11-08 03:30:40 - ? [124] Subsystem 'Merge' successfully loaded (maximum
concurrency: 100)
2006-11-08 03:31:10 - ? [124] Subsystem 'ActiveScripting' successfully
loaded (maximum concurrency: 10)
2006-11-08 03:31:10 - ? [124] Subsystem 'QueueReader' successfully loaded
(maximum concurrency: 100)
2006-11-08 03:31:10 - ? [124] Subsystem 'LogReader' successfully loaded
(maximum concurrency: 25)
2006-11-08 03:31:10 - ? [129] SQLAgent$[INSTANCE] starting under Windows NT
service control
2006-11-08 03:31:10 - + [260] Unable to start mail session (reason: No mail
profile defined)
2006-11-08 03:31:10 - ? [174] Job scheduler engine started (maximum worker
threads: 0)
2006-11-08 03:31:10 - ? [146] Request servicer engine started
2006-11-08 03:31:10 - ? [167] Populating job cache...
2006-11-08 03:31:10 - + [396] An idle CPU condition has not been defined -
OnIdle job schedules will have no effect
2006-11-08 03:31:10 - ? [133] Support engine started
2006-11-08 03:31:10 - ? [193] Alert engine started (using Eventlog Events)
2006-11-08 03:31:10 - ? [168] There are 0 job(s) [0 disabled] in the job cache
2006-11-08 03:31:10 - ? [170] Populating alert cache...
2006-11-08 03:31:10 - ? [171] There are 9 alert(s) in the alert cache
The machine is a very high spec machine and there's a lot of cpu/memory
available.
Thanks
It looks like it is hanging on ActiveScripting which is part of DTS. Does
this help you to resolve it?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kunal" <Kunal@.discussions.microsoft.com> wrote in message
news:C42254BF-88A3-49E5-A461-27B98EF8687D@.microsoft.com...
> Hi,
> On a number of servers we are facing issues regarding the SQL Server Agent
> service. The service is experiencing a delay during startup, more than the
> wait hint period. THe service should ideally be starting in 30 seconds (Or
> it
> seems to say so in the Wait Hint). But it is taking around 1min. Our
> software
> thinks it is a timeout and raises an error.
> Following is the SQLAgent log file of when the service is starting:
> 2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.760
> (x86
> unicode retail build) : Process ID
> 2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.760
> (x86
> unicode retail build) : Process ID 1956
> 2006-11-08 03:30:10 - ? [101] SQL Server [MACHINE_NAME]\[INSTANCE] version
> 8.00.760 (0 connection limit)
> 2006-11-08 03:30:10 - ? [102] SQL Server ODBC driver version 3.81.9031
> 2006-11-08 03:30:10 - ? [103] NetLib being used by driver is DBMSLPCN.DLL;
> Local host server is [MACHINE_NAME]\[INSTANCE]
> 2006-11-08 03:30:10 - ? [310] 2 processor(s) and 1023 MB RAM detected
> 2006-11-08 03:30:10 - ? [339] Local computer is [MACHINE_NAME] running
> Windows NT 5.0 (2195) Service Pack 3
> 2006-11-08 03:30:10 - ? [124] Subsystem 'TSQL' successfully loaded
> (maximum
> concurrency: 20)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'CmdExec' successfully loaded
> (maximum concurrency: 10)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'Snapshot' successfully loaded
> (maximum concurrency: 100)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'Distribution' successfully loaded
> (maximum concurrency: 100)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'Merge' successfully loaded
> (maximum
> concurrency: 100)
> 2006-11-08 03:31:10 - ? [124] Subsystem 'ActiveScripting' successfully
> loaded (maximum concurrency: 10)
> 2006-11-08 03:31:10 - ? [124] Subsystem 'QueueReader' successfully loaded
> (maximum concurrency: 100)
> 2006-11-08 03:31:10 - ? [124] Subsystem 'LogReader' successfully loaded
> (maximum concurrency: 25)
> 2006-11-08 03:31:10 - ? [129] SQLAgent$[INSTANCE] starting under Windows
> NT
> service control
> 2006-11-08 03:31:10 - + [260] Unable to start mail session (reason: No
> mail
> profile defined)
> 2006-11-08 03:31:10 - ? [174] Job scheduler engine started (maximum worker
> threads: 0)
> 2006-11-08 03:31:10 - ? [146] Request servicer engine started
> 2006-11-08 03:31:10 - ? [167] Populating job cache...
> 2006-11-08 03:31:10 - + [396] An idle CPU condition has not been defined -
> OnIdle job schedules will have no effect
> 2006-11-08 03:31:10 - ? [133] Support engine started
> 2006-11-08 03:31:10 - ? [193] Alert engine started (using Eventlog Events)
> 2006-11-08 03:31:10 - ? [168] There are 0 job(s) [0 disabled] in the job
> cache
> 2006-11-08 03:31:10 - ? [170] Populating alert cache...
> 2006-11-08 03:31:10 - ? [171] There are 9 alert(s) in the alert cache
>
> The machine is a very high spec machine and there's a lot of cpu/memory
> available.
> Thanks
sql

Delay in SQLAgent Service startup

Hi,
On a number of servers we are facing issues regarding the SQL Server Agent
service. The service is experiencing a delay during startup, more than the
wait hint period. THe service should ideally be starting in 30 seconds (Or i
t
seems to say so in the Wait Hint). But it is taking around 1min. Our softwar
e
thinks it is a timeout and raises an error.
Following is the SQLAgent log file of when the service is starting:
2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.760
(x86
unicode retail build) : Process ID
2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.760
(x86
unicode retail build) : Process ID 1956
2006-11-08 03:30:10 - ? [101] SQL Server [MACHINE_NAME]\[INSTANC
E] version
8.00.760 (0 connection limit)
2006-11-08 03:30:10 - ? [102] SQL Server ODBC driver version 3.81.9031
2006-11-08 03:30:10 - ? [103] NetLib being used by driver is DBMSLPCN.DL
L;
Local host server is [MACHINE_NAME]\[INSTANCE]
2006-11-08 03:30:10 - ? [310] 2 processor(s) and 1023 MB RAM detected
2006-11-08 03:30:10 - ? [339] Local computer is [MACHINE_NAME] runni
ng
Windows NT 5.0 (2195) Service Pack 3
2006-11-08 03:30:10 - ? [124] Subsystem 'TSQL' successfully loaded (maxi
mum
concurrency: 20)
2006-11-08 03:30:40 - ? [124] Subsystem 'CmdExec' successfully loaded
(maximum concurrency: 10)
2006-11-08 03:30:40 - ? [124] Subsystem 'Snapshot' successfully loaded
(maximum concurrency: 100)
2006-11-08 03:30:40 - ? [124] Subsystem 'Distribution' successfully load
ed
(maximum concurrency: 100)
2006-11-08 03:30:40 - ? [124] Subsystem 'Merge' successfully loaded (max
imum
concurrency: 100)
2006-11-08 03:31:10 - ? [124] Subsystem 'ActiveScripting' successfully
loaded (maximum concurrency: 10)
2006-11-08 03:31:10 - ? [124] Subsystem 'QueueReader' successfully loade
d
(maximum concurrency: 100)
2006-11-08 03:31:10 - ? [124] Subsystem 'LogReader' successfully loaded
(maximum concurrency: 25)
2006-11-08 03:31:10 - ? [129] SQLAgent$[INSTANCE] starting under Win
dows NT
service control
2006-11-08 03:31:10 - + [260] Unable to start mail session (reason: No m
ail
profile defined)
2006-11-08 03:31:10 - ? [174] Job scheduler engine started (maximum work
er
threads: 0)
2006-11-08 03:31:10 - ? [146] Request servicer engine started
2006-11-08 03:31:10 - ? [167] Populating job cache...
2006-11-08 03:31:10 - + [396] An idle CPU condition has not been defined
-
OnIdle job schedules will have no effect
2006-11-08 03:31:10 - ? [133] Support engine started
2006-11-08 03:31:10 - ? [193] Alert engine started (using Eventlog Event
s)
2006-11-08 03:31:10 - ? [168] There are 0 job(s) [0 disabled] in the
job cache
2006-11-08 03:31:10 - ? [170] Populating alert cache...
2006-11-08 03:31:10 - ? [171] There are 9 alert(s) in the alert cache
---
The machine is a very high spec machine and there's a lot of cpu/memory
available.
ThanksIt looks like it is hanging on ActiveScripting which is part of DTS. Does
this help you to resolve it?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kunal" <Kunal@.discussions.microsoft.com> wrote in message
news:C42254BF-88A3-49E5-A461-27B98EF8687D@.microsoft.com...
> Hi,
> On a number of servers we are facing issues regarding the SQL Server Agent
> service. The service is experiencing a delay during startup, more than the
> wait hint period. THe service should ideally be starting in 30 seconds (Or
> it
> seems to say so in the Wait Hint). But it is taking around 1min. Our
> software
> thinks it is a timeout and raises an error.
> Following is the SQLAgent log file of when the service is starting:
> 2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.76
0
> (x86
> unicode retail build) : Process ID
> 2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.76
0
> (x86
> unicode retail build) : Process ID 1956
> 2006-11-08 03:30:10 - ? [101] SQL Server [MACHINE_NAME]\[INSTA
NCE] version
> 8.00.760 (0 connection limit)
> 2006-11-08 03:30:10 - ? [102] SQL Server ODBC driver version 3.81.9031
> 2006-11-08 03:30:10 - ? [103] NetLib being used by driver is DBMSLPCN.
DLL;
> Local host server is [MACHINE_NAME]\[INSTANCE]
> 2006-11-08 03:30:10 - ? [310] 2 processor(s) and 1023 MB RAM detected
> 2006-11-08 03:30:10 - ? [339] Local computer is [MACHINE_NAME] run
ning
> Windows NT 5.0 (2195) Service Pack 3
> 2006-11-08 03:30:10 - ? [124] Subsystem 'TSQL' successfully loaded
> (maximum
> concurrency: 20)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'CmdExec' successfully loaded
> (maximum concurrency: 10)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'Snapshot' successfully loaded
> (maximum concurrency: 100)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'Distribution' successfully lo
aded
> (maximum concurrency: 100)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'Merge' successfully loaded
> (maximum
> concurrency: 100)
> 2006-11-08 03:31:10 - ? [124] Subsystem 'ActiveScripting' successfully
> loaded (maximum concurrency: 10)
> 2006-11-08 03:31:10 - ? [124] Subsystem 'QueueReader' successfully loa
ded
> (maximum concurrency: 100)
> 2006-11-08 03:31:10 - ? [124] Subsystem 'LogReader' successfully loade
d
> (maximum concurrency: 25)
> 2006-11-08 03:31:10 - ? [129] SQLAgent$[INSTANCE] starting under W
indows
> NT
> service control
> 2006-11-08 03:31:10 - + [260] Unable to start mail session (reason: No
> mail
> profile defined)
> 2006-11-08 03:31:10 - ? [174] Job scheduler engine started (maximum wo
rker
> threads: 0)
> 2006-11-08 03:31:10 - ? [146] Request servicer engine started
> 2006-11-08 03:31:10 - ? [167] Populating job cache...
> 2006-11-08 03:31:10 - + [396] An idle CPU condition has not been defin
ed -
> OnIdle job schedules will have no effect
> 2006-11-08 03:31:10 - ? [133] Support engine started
> 2006-11-08 03:31:10 - ? [193] Alert engine started (using Eventlog Eve
nts)
> 2006-11-08 03:31:10 - ? [168] There are 0 job(s) [0 disabled] in t
he job
> cache
> 2006-11-08 03:31:10 - ? [170] Populating alert cache...
> 2006-11-08 03:31:10 - ? [171] There are 9 alert(s) in the alert cache
> ---
> The machine is a very high spec machine and there's a lot of cpu/memory
> available.
> Thanks

Delay in SQLAgent Service startup

Hi,
On a number of servers we are facing issues regarding the SQL Server Agent
service. The service is experiencing a delay during startup, more than the
wait hint period. THe service should ideally be starting in 30 seconds (Or it
seems to say so in the Wait Hint). But it is taking around 1min. Our software
thinks it is a timeout and raises an error.
Following is the SQLAgent log file of when the service is starting:
2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86
unicode retail build) : Process ID
2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86
unicode retail build) : Process ID 1956
2006-11-08 03:30:10 - ? [101] SQL Server [MACHINE_NAME]\[INSTANCE] version
8.00.760 (0 connection limit)
2006-11-08 03:30:10 - ? [102] SQL Server ODBC driver version 3.81.9031
2006-11-08 03:30:10 - ? [103] NetLib being used by driver is DBMSLPCN.DLL;
Local host server is [MACHINE_NAME]\[INSTANCE]
2006-11-08 03:30:10 - ? [310] 2 processor(s) and 1023 MB RAM detected
2006-11-08 03:30:10 - ? [339] Local computer is [MACHINE_NAME] running
Windows NT 5.0 (2195) Service Pack 3
2006-11-08 03:30:10 - ? [124] Subsystem 'TSQL' successfully loaded (maximum
concurrency: 20)
2006-11-08 03:30:40 - ? [124] Subsystem 'CmdExec' successfully loaded
(maximum concurrency: 10)
2006-11-08 03:30:40 - ? [124] Subsystem 'Snapshot' successfully loaded
(maximum concurrency: 100)
2006-11-08 03:30:40 - ? [124] Subsystem 'Distribution' successfully loaded
(maximum concurrency: 100)
2006-11-08 03:30:40 - ? [124] Subsystem 'Merge' successfully loaded (maximum
concurrency: 100)
2006-11-08 03:31:10 - ? [124] Subsystem 'ActiveScripting' successfully
loaded (maximum concurrency: 10)
2006-11-08 03:31:10 - ? [124] Subsystem 'QueueReader' successfully loaded
(maximum concurrency: 100)
2006-11-08 03:31:10 - ? [124] Subsystem 'LogReader' successfully loaded
(maximum concurrency: 25)
2006-11-08 03:31:10 - ? [129] SQLAgent$[INSTANCE] starting under Windows NT
service control
2006-11-08 03:31:10 - + [260] Unable to start mail session (reason: No mail
profile defined)
2006-11-08 03:31:10 - ? [174] Job scheduler engine started (maximum worker
threads: 0)
2006-11-08 03:31:10 - ? [146] Request servicer engine started
2006-11-08 03:31:10 - ? [167] Populating job cache...
2006-11-08 03:31:10 - + [396] An idle CPU condition has not been defined -
OnIdle job schedules will have no effect
2006-11-08 03:31:10 - ? [133] Support engine started
2006-11-08 03:31:10 - ? [193] Alert engine started (using Eventlog Events)
2006-11-08 03:31:10 - ? [168] There are 0 job(s) [0 disabled] in the job cache
2006-11-08 03:31:10 - ? [170] Populating alert cache...
2006-11-08 03:31:10 - ? [171] There are 9 alert(s) in the alert cache
---
The machine is a very high spec machine and there's a lot of cpu/memory
available.
ThanksIt looks like it is hanging on ActiveScripting which is part of DTS. Does
this help you to resolve it?
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kunal" <Kunal@.discussions.microsoft.com> wrote in message
news:C42254BF-88A3-49E5-A461-27B98EF8687D@.microsoft.com...
> Hi,
> On a number of servers we are facing issues regarding the SQL Server Agent
> service. The service is experiencing a delay during startup, more than the
> wait hint period. THe service should ideally be starting in 30 seconds (Or
> it
> seems to say so in the Wait Hint). But it is taking around 1min. Our
> software
> thinks it is a timeout and raises an error.
> Following is the SQLAgent log file of when the service is starting:
> 2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.760
> (x86
> unicode retail build) : Process ID
> 2006-11-08 03:30:10 - ? [100] Microsoft SQLServerAgent version 8.00.760
> (x86
> unicode retail build) : Process ID 1956
> 2006-11-08 03:30:10 - ? [101] SQL Server [MACHINE_NAME]\[INSTANCE] version
> 8.00.760 (0 connection limit)
> 2006-11-08 03:30:10 - ? [102] SQL Server ODBC driver version 3.81.9031
> 2006-11-08 03:30:10 - ? [103] NetLib being used by driver is DBMSLPCN.DLL;
> Local host server is [MACHINE_NAME]\[INSTANCE]
> 2006-11-08 03:30:10 - ? [310] 2 processor(s) and 1023 MB RAM detected
> 2006-11-08 03:30:10 - ? [339] Local computer is [MACHINE_NAME] running
> Windows NT 5.0 (2195) Service Pack 3
> 2006-11-08 03:30:10 - ? [124] Subsystem 'TSQL' successfully loaded
> (maximum
> concurrency: 20)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'CmdExec' successfully loaded
> (maximum concurrency: 10)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'Snapshot' successfully loaded
> (maximum concurrency: 100)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'Distribution' successfully loaded
> (maximum concurrency: 100)
> 2006-11-08 03:30:40 - ? [124] Subsystem 'Merge' successfully loaded
> (maximum
> concurrency: 100)
> 2006-11-08 03:31:10 - ? [124] Subsystem 'ActiveScripting' successfully
> loaded (maximum concurrency: 10)
> 2006-11-08 03:31:10 - ? [124] Subsystem 'QueueReader' successfully loaded
> (maximum concurrency: 100)
> 2006-11-08 03:31:10 - ? [124] Subsystem 'LogReader' successfully loaded
> (maximum concurrency: 25)
> 2006-11-08 03:31:10 - ? [129] SQLAgent$[INSTANCE] starting under Windows
> NT
> service control
> 2006-11-08 03:31:10 - + [260] Unable to start mail session (reason: No
> mail
> profile defined)
> 2006-11-08 03:31:10 - ? [174] Job scheduler engine started (maximum worker
> threads: 0)
> 2006-11-08 03:31:10 - ? [146] Request servicer engine started
> 2006-11-08 03:31:10 - ? [167] Populating job cache...
> 2006-11-08 03:31:10 - + [396] An idle CPU condition has not been defined -
> OnIdle job schedules will have no effect
> 2006-11-08 03:31:10 - ? [133] Support engine started
> 2006-11-08 03:31:10 - ? [193] Alert engine started (using Eventlog Events)
> 2006-11-08 03:31:10 - ? [168] There are 0 job(s) [0 disabled] in the job
> cache
> 2006-11-08 03:31:10 - ? [170] Populating alert cache...
> 2006-11-08 03:31:10 - ? [171] There are 9 alert(s) in the alert cache
> ---
> The machine is a very high spec machine and there's a lot of cpu/memory
> available.
> Thanks

degraded stored procedure performance

Hi,

I have been experiencing an intermittent problem that I hope someone can help me with.

Twice over the last month or so, we have experienced a problem where the performance of a single stored procedure degrades dramatically very quickly, possibly instantaneously from ~1sec to ~15-25 secs. What's throwing me is there are hundreds of other stored procedures, but none of them has been affected. Is there a possibility that our Maintenance plan which is scheduled to reorganize the data and index pages on Sunday night be the culprit?? Both times the problem reared it's ugly head on Monday that's why I'm wondering if it is causing some problem with the sp's execution plan or something, because the problem goes away if I recompile the stored procedure. If it is the problem, I have a couple more questions, what can I do to help prevent it from occurring in the future, and why does it only affect one sp?? If however you don't think it is the cause any other thoughts would be greatly appreciated.

The stored procedure in question has not been modified for 2 months and generally performs fine.

SQL Server 2000 Enterprise Edition 8.00.679

Thanks in AdvanceWhat you have describe is not that uncommon. This would most likely happen if the size of the underlying table(s) grew or shrank significantly after the sp was compiled or if the data distibution drastically changed after the sp was compiled.

One thing you might want to do is force a recompile of all sp and triggers after the maintinance plan runs check out 'sp_recompile' in BOL.|||to step though all tables you can use:

Microsofts code:
sp_MSforeachtable 'sp_recompile ''?'''

Or your own:
declare @.Tbl sysname
select @.Tbl = min(name) from sysobjects where type = 'U'
while (@.Tbl is not null) begin
exec('sp_recompile ' + @.Tbl)
select @.Tbl = min(name) from sysobjects where type = 'U' and name > @.Tbl
end