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 23 Mar 2010 20:12 Here is @@version: Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) Mar 29 2009 10:11:52 Copyright (c) 1988-2008 Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) I think I have figured out the update system. It seems like the hotfix rollups are beta versions of fixes that will eventually appear in the next service pack. Since they are betas, MS recommends against deployment in production without extensive prior testing. That's also the reason it takes a special request to get them. It seems that in general, people prefer not to upgrade until an official SP is released, and won't install any hotfixes unless they are critical to their particular operation. Also, it looks like SP2 will come out in early fall. Of course, none of that addresses my question. But at least I learned something. "Chris Wood" <anonymous(a)microsoft.com> wrote in message news:%23lEXVvpyKHA.5040(a)TK2MSFTNGP02.phx.gbl... > 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? >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> >> >> > >
From: Chris Wood on 24 Mar 2010 11:23
Paul, We have used CU's here (SQL2005 only) because they fix some situations that we have and in most cases they are stable enough. If you notice they come out every 2 months and if a previous one has a regression issue it should at least be acknowledged in the next CU. If you cannot wait for SP2 but can try out and test a CU, CU8 will appear in mid May. They are now easy to get as at the top of the KB for the CU there is a View and request hotix downloads link. Just click it and make sure you request the correct version (32_bit/64_bit) because it defaults to the version of the machine you are making the request from. So if you want 64_bit but are on a 32_but O/S click at 1 Show hotfixes for all platforms and languages. HTH Chris "Paul Pedersen" <nospam(a)no.spam> wrote in message news:u%23gb5auyKHA.2552(a)TK2MSFTNGP04.phx.gbl... > Here is @@version: > > Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) > Mar 29 2009 10:11:52 > Copyright (c) 1988-2008 Microsoft Corporation > Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) > > > I think I have figured out the update system. It seems like the hotfix > rollups are beta versions of fixes that will eventually appear in the next > service pack. Since they are betas, MS recommends against deployment in > production without extensive prior testing. That's also the reason it > takes a special request to get them. > > It seems that in general, people prefer not to upgrade until an official > SP is released, and won't install any hotfixes unless they are critical to > their particular operation. > > Also, it looks like SP2 will come out in early fall. > > > Of course, none of that addresses my question. But at least I learned > something. > > > > > > "Chris Wood" <anonymous(a)microsoft.com> wrote in message > news:%23lEXVvpyKHA.5040(a)TK2MSFTNGP02.phx.gbl... >> 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? >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >> >> > > > |