For a Microsoft Exchange version of this article, see the following article in the Microsoft Knowledge Base:
For a Microsoft Windows version of this article, see the following article in the Microsoft Knowledge Base:
A software update package is an executable (.exe or .msi) file that contains one or more files that may be applied to Microsoft SQL Server installations to correct a specific problem. Software update packages are distributed by Microsoft Customer Support Services (CSS) to customers whose computers are affected by a specific problem.
Microsoft has adopted a naming schema for software update packages for the following reasons:
- Creates consistency across Microsoft software update packages
- Easier to search for software updated packages and Knowledge Base articles
- Clear identification of the language and SQL Server version for which the software update package are applicable
Package information and release typesEach software update package that is selected at download time is contained within a self-extracting executable that facilitates easy installation and deployment of the software update package.
SQL Server software update packages typically fall into two major release types:
- GDR (General Distribution Release): GDR releases are reserved for those key fixes identified by SQL Server support to potentially affect a broad customer base.
- Hotfix: Hotfix releases are typically for fixes to isolated issues not affecting a large customer base; while the product is in mainstream support. Hotfix are released in two major types:
- COD (Critical On Demand) or OD (On Demand): COD or OD releases are reserved for critical customer requests where key business functionality is impaired from the issue encountered. As the nature of the request, these releases do not follow a regular cadence.
- CU (Cumulative Update): CU releases are non critical requests which provide fixes for isolated issues not affecting key business functionality. The CU releases on a two-month cadence while the product and service pack are in mainstream support.
Packages and file naming schema
Naming schema for SQL Server software update packagesSQL Server software update packages can be easily identified using the following naming schema.
Software update package name schemaTo distinguish between the various software update packages available online, the following schema is employed:
Extracted SQL Server file name schemaOnce the primary SQL Server software update package has been downloaded and extracted, the file name will resemble the following:
Extracted feature pack name schemaOnce a software update package for a feature pack has been downloaded and extracted, the file name will resemble the following:
- ProductName This is the full product name, which includes the product version information. For SQL Server, this attribute could be one of the following:
- SP number or RTM The service pack level of the product or component which it can be applied on top of. RTM indicates the product without any service packs installed.
- KB article number The Microsoft Knowledge Base article number that is associated with the software update.
- Servicing ReleaseThe release type for the software update. For details, visit the “Package information and release types” section.
- COD: Critical On Demand
- OD: On Demand
- CU: Cumulative Update followed by the cumulative update release number
- Architecture identifier This field is used to indicate on which processor architecture the particular hotfix package runs. The current options are the following:
- x86: This package runs on x86 platforms.
- ia64: This package runs on Itanium IA-64 platforms for 64-bit.
- x64: This package only runs on AMD x64 and compatible systems.
- x86: This package runs on x86 platforms.
- Version An optional field that indicates the version of the software release.
- Build number An optional field which is used to indicate the SQL Server build number included in the software update.
For example, in SQL2000-KB840223-8.00.1007-ia64-ENU.exe, the build version of SQL Server is 8.00.1007. This will correspond to the file version of Sqlservr.exe and to the returned value from @@version run against this server instance.
Software update package and extracted file name mappingThe following tables illustrates the mapping between the “Download File Name” on the hotfix download page and the actual name of the package once downloaded and extracted.
SQL Server software Update Package
|Package||Software Update Package Name||Extracted SQL Server File Name|
|CU Package for SQL Server 2005||SQLServer2005_SPx_CUxx_kbxxxxxx_9_00_xxxx_Arch||SQLServer2005-KBxxxxxxx-Arch-Lang.exe|
|CU Package for SQL Server 2008||SQLServer2008_RTM_CUxx_kbxxxxxx_10_00_xxxx_Arch|
|CU Package for SQL Server 2008 R2||SQLServer2008R2_RTM_CUxx_kbxxxxxx_10_50_xxxx_Arch|
|CU Package for SQL Server 2012||SQLServer2012_RTM_CUxx_kbxxxxxx_11_00_xxxx_Arch|
SQL Server Feature Pack
|Package||Software Update Package Name||Extracted SQL Server File Name|
|SQL Native Client||2005_SPx_SNAC_CUxx_kbxxxxxx_9_00_xxxx_Arch |
|AS OLE DB for SQL Server 2005||2005_SPx_ASOLEDB_CUxx_kbxxxxxx_9_00_xxxx_Arch||SQLServer2005_ASOLEDB9.msi|
|AS OLE DB for SQL Server 2008||2008_RTM_ASOLEDB_CUxx_kbxxxxxx_10_00_xxxx_Arch |
|AS OLE DB for SQL Server 2012||2012_RTM_ASOLEDB_CUxx_kbxxxxxx_11_00_xxxx_Arch |
|XMO/SMO (Shared Management Objects) for SQL Server 2005||2005_SPx_XMO_CUxx_kbxxxxxx_9_00_xxxx_Arch||SQLServer2005_XMO.msi|
|XMO/SMO (Shared Management Objects) for SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012||2008_RTM_SMO_CUxx_kbxxxxxx_10_00_xxxx_Arch |
|Reporting Services for SharePoint for SQL Server 2005||2005_SPx_RSShrPnt_CUxx_KBxxxxx_9_00_xxxx_arch||SharePointRS.msi|
|Reporting Services for SharePoint for SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012||2008_RTM_RSShrPnt_CUxx_KBxxxxx_10_00_xxxx_arch |
|rsSharePoint.msi (x86 and x64 only)|
|Reporting Services for SharePoint for SQL Server 2008 R2||2008R2_RTM_RSShrPnt_CUxx_KBxxxxx_10_50_xxxx_arch|
|rsSharePoint.msi (x64 only)|
|Report Builder Click Once||2008_RTM_RBClckOnc_CUxx_kbxxxxx_10_00_xxxx_Arch |
|RB2ClickOnce.msi (x86 and x64 only)|
|Report Builder for SQL Server 2008||2008_RTM_RprtBlder_CUxx_KBxxxx_10_00_xxxx_Arch |
|ReportBuilder.msi (x86 only)|
|Report Builder for SQL Server 2008 R2||2008R2_RTM_RprtBlder_CUxx_KBxxxx_10_50_xxxx_Arch|
|Sap BI||2008_RTM_SapBI_CUxx_kbxxxxxx_10_00_xxxx_Arch |
|PowerPivot for Excel Client||2008R2_RTM_PPExcel_CUxx_KBxxxxx_10_50_xxxx_arch|
|Stream Insight and Server||2008R2_RTM_PPServer_CUxx_KBxxxxx_10_50_xxxx_arch|
|Master Data Services||2008R2_RTM_MDS_CUxx_KBxxxxx_10_50_xxxx_arch|
|MasterDataServices.msi (x64 only)|
|Data-Tier Application Framework||2012_RTM_DAC_CUxx_KBxxxxx_11_00_xxxx_arch|
|Transact-SQL Language Service||2012_RTM_TSQLLAN_CUxx_KBxxxxx_11_00_xxxx_arch|
Best practices As a best practice, consider providing a name that you can use to easily identify packages during downloads.
Package descriptionsThis section describes each of the packages that are listed and their purposes. Installing a newer MSI package over an older MSI package removes the older version in favor of the newer version. Uninstalling a feature pack update by using an MSI package will completely remove the component. However, for the main CU package, uninstalling the .exe file causes a rollback to the previously installed version.
SQL Server software update packageFile name
SQLServer2008R2-kbxxxxxx-Arch (For SQL Server 2008 R2)
SQLServer2012-kbxxxxxx-Arch (For SQL Server 2012)
Purpose The SQL Server software update package will update the SQL Server instance by using a collection of all SQL Server hotfixes that have been created since the product was released. The package will apply updates to all installed components if an update has been made. This package will update SQL Server DB & Engine, Analysis Service, Integration Services, Reporting Services, Replication Engine, and Manageability.
SQL Server Native ClientFile name
Report builderFile name
ReportBuilder3.msi (For SQL Server 2008 R2)
Report Builder Click OnceFile name
Reporting Services for SharePointFile name
SQL WriterFile name
AS OLE DBFile name
XMO/SMO (Shared Management Objects)File name
Stream Insight (client)File name
Stream Insight (Server)File name
PowerPivot Excel ClientFile name
Master Data ServicesFilename
Data-Tier Application FrameworkFilename
OLEDB Provider for DB2Filename
DB2OLEDBV4.msi (For SQL Server 2012)
Transact-SQL Language ServiceFilename
|Fix area||A fix in this area can address issues related to (but not limited to)|
|Analysis Services (SSAS)||Issues or errors that are related to any operations or components of Analysis Services (for example, processing a cube, exceptions when you use analysis services components and so on).|
|Connectivity||Issues or errors that may occur when a program connects to SQL server that are caused by a bug or a problem with Client provider (such as System.Data, SQL OLE DB and so on).|
|Data Quality Services (DQS)||Issues or errors when you use DQS or its components.|
|High Availability||Always On, Clustering, Logshipping, Database mirroring and so on|
|Integration services (SSIS)||Issues or errors together with components that are related to SSIS (such as BI studio, SSIS service and so on).|
|Management Tools||Issues or errors when you use various SQL server tools (such as SQL Server management studio, Profiler, Database Engine Tuning Advisor and other SQL client tools).|
|Master Data Services (MDS)||Issues or errors when you use MDS and its components.|
|Reporting services (SSRS)||Issues or errors when you use Reporting services components (such as Report server, Report manager, Report designer and so on).|
|Setup and Install||Issues or errors for installing SQL Server or any of its components.|
|SQL performance||Query or server-wide performance issues.|
|SQL security||Issues or errors for authentication, authorization, Transparent Data Encryption (TDE), Auditing, FIPS compliance, Server hardening and so on.|
|SQL Service||Issues when you use AVS, exceptions, non-yielding schedulers, Server stops responding, DBCC checks, backup or restore operations, Database mirroring, Database recovery, memory leaks, corruption, distributed or linked server queries, Replication and so on.|
|XML||Any issues that are related to MSXML, System.XML, XML Lite and so on.|
Frequently asked questions
- I have SQL Server 2008. Do I need to apply both the SQL Server software update package and the SQL Server Native Client package on the server to get all SNAC fixes (e.g., consider linked server scenario where server is also a client)?
If client and server are on the same machine, individually installing the SQL Server Native Client package is not required. If client and server are separate, apply the SQL Native Client package to the client, and apply the SQL Server Software Update Package to the server to get all updates.
- I have SQL Server 2005. Do I need to apply both the SQL Server software update package and the SQL Server Native Client package on the server to get all SNAC fixes?
Yes, both the SQL Server software update package and SQL Native Client Package are required to update the server and must be downloaded separately.
- Do I need to install the Feature Pack and the SQL Server Software Update Package?
Each KB article will clearly identify the packages which need to be applied to the computer to obtain the described fix. SNAC and other MSI’s (SQLWriter, XMO, RS Sharepoint, RB Clickonce etc.) are version bumped every CU even if there are no new fixes.
- How will we adjust the KB’s once we reach 999999?
Our KB’s are currently 6 digits but will be going to 7 soon. The schema shown above in this doc is using the Letter’s KB plus 5 X’s for a total of 7 characters to show our expected schema once we cross the 1,000,000 mark. Until such time do continue to use the given 6 digit KB.
- How do I apply the SQLWriter.msi feature pack?
At this time you will need to run the SQLWriter.msi after the CU or COD package that you have downloaded for you fix.
Article ID: 822499 - Last Review: Mar 12, 2014 - Revision: 1