SharePoint depends on SQL Server 2005. Therefore, keeping SQL Server 2005 patched is something every developer should be aware of.
You may think putting Service Pack 3 (SP3) on is all you need to do to keep SQL Server 2005 up-to-date. Not true. To understand how/why Microsoft delivers fixes for SQL Server 2005, the support article that describes SQL Server Incremental Servicing Model is a “must read”, not just for DBA’s, but anybody who deals with SQL Server 2005, even indirectly (e.g., SharePoint administrator or SharePoint developer).
While I’m at it, visit The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released. In addition to information about the three releases of “post-SP3 cumulative update packages”, you’ll see the latest SQL Server 2005 internal numbering.
To see what version of SQL Server 2005 you are running, run the following query:
SET NOCOUNT ON;
SELECT serverproperty('Edition') [Edition],
CASE serverproperty('EngineEdition')
WHEN 2 THEN 'Standard or Workgroup'
WHEN 3 THEN 'Enterprise, Enterprise Evaluation, or Developer'
WHEN 4 THEN 'Express, Express Edition with Advanced Services, or Windows Embedded SQL'
ELSE '{unknown}'
END [Engine Edition],
serverproperty('ProductVersion') [Product Version],
serverproperty('ProductLevel') [Product Level]
With just Service Pack 3 installed on my SharePoint development box, the output from the above command is:
Engine: Enterprise Edition
Engine Edition: Enterprise, Enterprise Evaluation, or Developer
Product Version: 9.00.4035.00
Product Level: SP3
The latest downloadable post-SP3 cumulative update package (#1) can be found here.
