Many resources (CPU, processes) even when idle
in [Server Configuration]
|
Prev: Official document about restoring SQL Server 2000 logs to SQL
Next: SSMS doesn't see SSAS or Integration Services in server type drop
From: Paul Pedersen on 22 Mar 2010 13:58 SQL Server seems to be making moderately large demands on the system even when it is idle. There are no connections and no scheduled tasks, yet SQL Server and Reporting Services together are using ~100 threads and up to 8% CPU. Is this normal? How can I tell it to let go of my processor and actually take a break when it's supposed to be idle?
From: Paul Pedersen on 22 Mar 2010 14:07 I should mention that this is SQL 2008. "Paul Pedersen" <nospam(a)no.spam> wrote in message news:uTwYRleyKHA.4492(a)TK2MSFTNGP05.phx.gbl... > SQL Server seems to be making moderately large demands on the system even > when it is idle. There are no connections and no scheduled tasks, yet SQL > Server and Reporting Services together are using ~100 threads and up to 8% > CPU. > > Is this normal? How can I tell it to let go of my processor and actually > take a break when it's supposed to be idle? > > >
From: Chris Wood on 22 Mar 2010 15:20 paul, is this your problem http://support.microsoft.com/kb/978430/ It's in SP1 CU7 just released. HTH Chris "Paul Pedersen" <nospam(a)no.spam> wrote in message news:%23q1CWqeyKHA.5940(a)TK2MSFTNGP02.phx.gbl... >I should mention that this is SQL 2008. > > > "Paul Pedersen" <nospam(a)no.spam> wrote in message > news:uTwYRleyKHA.4492(a)TK2MSFTNGP05.phx.gbl... >> SQL Server seems to be making moderately large demands on the system even >> when it is idle. There are no connections and no scheduled tasks, yet SQL >> Server and Reporting Services together are using ~100 threads and up to >> 8% CPU. >> >> Is this normal? How can I tell it to let go of my processor and actually >> take a break when it's supposed to be idle? >> >> >> > > >
From: Paul Pedersen on 22 Mar 2010 19:31 Thanks for the suggestion. I haven't had 100% use, but maybe this is it anyway. I don't understand this cumulative update system well. None of it seems to be handled by Microsoft Update. How can I tell which updates I already have? "Chris Wood" <anonymous(a)microsoft.com> wrote in message news:%23NXnLTfyKHA.3264(a)TK2MSFTNGP06.phx.gbl... > paul, > > is this your problem http://support.microsoft.com/kb/978430/ It's in SP1 > CU7 just released. > > HTH > > Chris > > "Paul Pedersen" <nospam(a)no.spam> wrote in message > news:%23q1CWqeyKHA.5940(a)TK2MSFTNGP02.phx.gbl... >>I should mention that this is SQL 2008. >> >> >> "Paul Pedersen" <nospam(a)no.spam> wrote in message >> news:uTwYRleyKHA.4492(a)TK2MSFTNGP05.phx.gbl... >>> SQL Server seems to be making moderately large demands on the system >>> even when it is idle. There are no connections and no scheduled tasks, >>> yet SQL Server and Reporting Services together are using ~100 threads >>> and up to 8% CPU. >>> >>> Is this normal? How can I tell it to let go of my processor and actually >>> take a break when it's supposed to be idle? >>> >>> >>> >> >> >> > >
From: Chris Wood on 23 Mar 2010 11:16
Paul, What build of SQL2008 are you running? Chris "Paul Pedersen" <nospam(a)no.spam> wrote in message news:eay9QfhyKHA.244(a)TK2MSFTNGP06.phx.gbl... > Thanks for the suggestion. I haven't had 100% use, but maybe this is it > anyway. > > I don't understand this cumulative update system well. None of it seems to > be handled by Microsoft Update. How can I tell which updates I already > have? > > > > > "Chris Wood" <anonymous(a)microsoft.com> wrote in message > news:%23NXnLTfyKHA.3264(a)TK2MSFTNGP06.phx.gbl... >> paul, >> >> is this your problem http://support.microsoft.com/kb/978430/ It's in SP1 >> CU7 just released. >> >> HTH >> >> Chris >> >> "Paul Pedersen" <nospam(a)no.spam> wrote in message >> news:%23q1CWqeyKHA.5940(a)TK2MSFTNGP02.phx.gbl... >>>I should mention that this is SQL 2008. >>> >>> >>> "Paul Pedersen" <nospam(a)no.spam> wrote in message >>> news:uTwYRleyKHA.4492(a)TK2MSFTNGP05.phx.gbl... >>>> SQL Server seems to be making moderately large demands on the system >>>> even when it is idle. There are no connections and no scheduled tasks, >>>> yet SQL Server and Reporting Services together are using ~100 threads >>>> and up to 8% CPU. >>>> >>>> Is this normal? How can I tell it to let go of my processor and >>>> actually take a break when it's supposed to be idle? >>>> >>>> >>>> >>> >>> >>> >> >> > > > |