Microsoft Virtualization Best Practices for SQL Server

Virtualizing business-critical applications delivers significant customer benefits, including cost savings, enhanced business continuity, and an agile and efficient management solution. In this webcast, we focus on virtualizing Microsoft SQL Server using Microsoft solutions, we discuss the benefits of using Microsoft virtualization technologies instead of technologies from key competitors such as VMware, and we provide guidance and technical best practices for virtualizing SQL Server in various production, test, and development scenarios.

The article continues at http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032428763&EventCategory=4&culture=en-US&CountryCode=US

Security update for SQL Server KB970892 fails to install

Over the last few days KB970892 has consitently failed to install on our SQL Servers via Windows Update. The following instructions will get it working.

Once the update fails to install, you’ll likely have to reboot as the system will be flagged as pending a reboot. Once rebooted we need to attempt to complete the SQL Server installation:

  1. Open up Add or Remove Programs, select Microsoft SQL Server 2005 and click Change
  2. On the Component Selection screen, choose Database Engine under SQL Server 2005 Instances and click Next
  3. On the Feature Maintenance screen, choose Database Engine and click Next
  4. Go through the setup wizard until the Change or Remove Instance screen. Then click Complete the suspended installation.
  5. Follow through the wizard, if you get a prompt for the files point it at your SQL SP3 installation media and continue.
[Warning]If you’re using SQL Server 2005 Express you can extract SQLEXPR32.EXE with the /x switch.

The installation will likely fail with the following error:

SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet Windows policy requirements because it is too short.. To continue, correct the problem, and then run SQL Server Setup again.

Edit C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\sqlagent90_msdb_upgrade.sql with notepad or similar.

Change password on line 30683 to something more complex, from:
encryption by password = 'Yukon90_'
To (for example):
encryption by password = 'Yukon90_23423ASDzz}{'

Then further down, change line 30977 to reflect the same value:

From
set @exec_str = N'add signature to ' + @sp + N' by certificate [##MS_AgentSigningCertificate##] with password = ''Yukon90_'''

To
set @exec_str = N'add signature to ' + @sp + N' by certificate [##MS_AgentSigningCertificate##] with password = ''Yukon90_23423ASDzz}{'''

Cancel out of setup. Back in Add or Remove Programs choose Change again for Microsoft SQL Server 2005 continuing through the wizard as before. This time, you wont get the error and the upgrade will complete.