Service pack 1 for SQL Server 2005 is out. Books OnLine and samples and sample databases are also refreshed. Here are all links you need.

 

Service Pack1:
http://www.microsoft.com/downloads/details.aspx?familyid=cb6c71ea-d649-47ff-9176-e7cac58fd4bc&displaylang=en
Books OnLine:
http://www.microsoft.com/downloads/thankyou.aspx?familyId=be6a2c5d-00df-4220-b133-29c1e0b6585f&displayLang=en&oRef
Samples:
http://www.microsoft.com/downloads/details.aspx?familyid=e719ecf7-9f46-4312-af89-6ad8702e4e6e&displaylang=en

A list of the new features and improvements that are included in SQL Server 2005 Service Pack 1 is at

http://support.microsoft.com/kb/916940

And finally, the Readme file for the SP 1 is at

http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/ReadmeSQL2005SP1.htm

 

I installed it for three times now, and always succeeded. You should be sure to shut down the Full Text service for the instance you are patching, and the SQL Browser service. I have to note that in one case I had to shut down the Integration Services service as well, but I don’t know exactly why. The setup procedure notified me I have some SSIS dll open exclusively by an application, and I found out the lock was held by the SSIS service. No client tool should be connected to any of the service you are patching. The update is based on “all-or-nothing” principle, which means you have to patch all services for the instance – Database Engine, Analysis Services, Integration Services and Reporting Services. I never managed to install the SP1 without need to reboot the computer. The native client and the database engine parts of installation needed the reboot. So be prepared, I guess you will have to reboot the machine as well.

After the installation, the version of all the services should be 9.0.2057. You can see the version in SSMS when you are connected to a particular service, with one exception: SSMS does not show the version of the Reporting Services. You can find it if you open the RS virtual directory directly in IE, UTL http://localhost/ReportServer. I would prefer if SSMS would show this number as well.

You can find all of the logs (very detailed logging!) from the setup at C:WINDOWSHotfix.

 

Finally, do not update the AdventureWorks and AdventureWorksDW databases yet, unless you use the case-sensitive version. The case-insensitive versions are accent-insensitive as well, and this is wrong and not in accordance with previous versions, which were accent-sensitive. If you use the new versions, you will not be able to process the AdventureWorks OLAP sample project.  I would really appreciate less problems with demo databases!

Dejan Sarka