Saturday, May 06, 2006

SysInternals EULA Updated

The SysInternals licensing has been updated on the SysInternals website. The new licensing is something you'll want to take a look at if you use these tools. There is a change with respect to "embedding" a SysInternals tool within another program, script, etc. You can find the new licensing agreement here:

http://www.sysinternals.com/Licensing.html

The portion that is catching everyone's attention is the following:

A commercial license is required to use the software in any way not covered above, including for example:

  • Redistributing the software in any manner, including by computer media, a file server, an email attachment, etc.
  • Embedding the software in or linking it to another program including internal applications, scripts, batch files, etc.
  • Use of the software for technical support on customer computers

The way I read this, if you use a script which calls a SysInternals product, you now need a commercial license. If that's the case, then something like the example given by Microsoft.com Operations would need just such a commercial license.

Friday, May 05, 2006

Scaling Out SQL Server 2005

This article appeared just recently on MSDN.

Scaling Out SQL Server 2005

It's a relatively high level document which covers how to think about the data before going with a scale out solution, what factors impact a scale out solution (such as how often the data is updated), and what the main options are.

Going to TechEd 2006 in Boston!

As of right now, it looks like I'm going to TechEd 2006 in Boston. If you're going to be there and want to meet up, let me know!

Monday, May 01, 2006

How Microsoft patches microsoft.com web servers

Microsoft.com operations has posted an interesting blog entry on how they patch their web servers:

Scripting Patch Management of Enterprise Web Clusters on Microsoft.com

I found a few things interesting in all of this:

  1. They are using Windows network load balancing instead of a 3rd party hardware load balancer. At least, they make no mention of such.
  2. They aren't using a fancy patch management product like those from Shavlik or St. Bernard Software.
  3. The core of their patching solution is a simple script written in VBScript.
  4. They are using psexec from Sysinternals.