DBAndrew's questions

Do I need a separate license for Windows Server 200X to run a warm standby server?

I have a Windows Server 2003 machine running SQL Server 2005. I also have a Windows Server 2008 machine running SQL Server 2005. I know I'm good on the SQL Server 2005 licensing to run a warm standby with log shipping. But I cannot find any documentation on licensing the windows 200X in this situation.

I'm planning on bringing up 1 new server running Windows Server 200X (2003 or 2008). The only thing this will be used for is Disaster Recovery. No users or apps will be talking to this server.

What is the best practice for the database owner in SQL Server 2005?

I have already searched this page...

http://technet.microsoft.com/en-us/sqlserver/bb331794.aspx

and didn't find what I was looking for.

This is the principals that is displayed in the owner column when you execute sp_helpdb and/or if you right click on the database in SSMS and select properties and go to "Files" it is the second drop down list box from the top labeled owner.

Currently it is set to a domain user who is no longer with the company. In the past I've always left it with the default which is the user that created it. I know I cannot set it to the domain user that the services run as. I could set it to SA but this feels wrong. Perhaps I should create a new special SQL Login that has limited permissions and just serves this purpose?

Why does Windows Automatic Updates ignore SQL Server service Packs?

Windows Server 2003 Standard X64 Service Pack 2

No WSUS server in the picture just Automatic Updates enabled.

Default install of SQL Server 2005 Standard and Automatic Updates won't display Service Packs for SQL Server. It shows all kinds of other critical security updates for the OS, IE, etc...