Windows 2003 Server

A little more information about the worm, from a technical point of view.  Now, from what I understand from Sam is that there is built in protection from these types of attacks.  Anyone running SQL Server (unpatched) out there on Windows 2003 Server that can tell me the results?  I'd give it a whirl myself, but our firewall "unfortunately" prevents me from infecting anything here.

My ASP.NET blog really has turned into a SQL Server blog.  Perhaps that's my niche.  I've been doing some thinking to datasets / disconnected data and what I'm teaching people in these SQL Server classes.  Most of the work is worrying about single update, delete or insert statements.  And the select statements are not really taking into account situations where we'd get all the Order info for one Employee.  It seems clustered indexes "best practice" of simply throwing it on the primary / identity field might not be the best thing in these cases.