RE: Slammer worm

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Rand Boyd [MSFT] (rboyd_at_onlinemicrosoft.com)
Date: 03/10/04 

Date: Wed, 10 Mar 2004 15:20:55 GMT

If you have Service Pack 3 or above for SQL Server 2000 successfully
applied then you are not being affect by Slammer, at least not because of
this machine. Verify that SQL Server SP3 or above is applied correctly by
running select @@version from Query Analyzer. Anything above build
2000.8.0.760 has the Slammer fix included.

Rand
This posting is provided "as is" with no warranties and confers no rights.

Relevant Pages

  • Re: MicroMonopoly aids Terrorism?
    ... >> Not if the patch makes it so you can't use SQL server. ... >> the multitudes of MS patches that get released. ... > No one is disputing that MS was hit by Slammer. ...
    (microsoft.public.security)
  • Re: Win32/SQLSlammer.virus
    ... Just a quick one regarding the Slammer; is MS SQL Server 7 ... >process which is using 90% or more CPU? ... >consuming huge amounts of memory. ...
    (microsoft.public.sqlserver.security)
  • Re: Win32/SQLSlammer.virus
    ... The best tools for determining if you are vulernable to the Slammer worm are ... That page also includes a link to the "SQL Server Critical Update Wizard", ... clicking on the "CPU" column twice to sort the display by the amount of CPU ...
    (microsoft.public.sqlserver.security)
  • Re: SQL thinks its Slammer
    ... Slammer exploits a known issue in the product and the fix address the issue ... Many SQL Server installations handle thousands of users concurrently. ... 2000 SP4 has the slammer fix, and if multiple queries are used the SQL ...
    (microsoft.public.sqlserver.security)
  • Re: SQL Server problem on sbs 2K3 + wss sp2
    ... but I have no idea if I'm running the latest service pack SP3a. ... I intended on *upgrading* from using MSDE for SharePoint to using SQL Server so I can do full-text searches and put the companyweb content on a NAS device. ... During the installation of SP3a, though, at step 4, I selected SharePoint and clicked next. ...
    (microsoft.public.windows.server.sbs)