This post is imparted from Here
Microsoft has adopted a standardized naming schema for all the software update packages for SQL Server that are created and distributed.
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 types
Each 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.
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
Packages and file naming schema
Naming schema for SQL Server software update packages
SQL Server software update packages can be easily identified using the following naming schema.Software update package name schema
To distinguish between the various software update packages available online, the following schema is employed:<product name or product program name>_<SP number or RTM>_<servicing release>_<KB article number>_<build number optional>_<architecture identifier>
Extracted SQL Server file name schema
Once the primary SQL Server software update package has been downloaded and extracted, the file name will resemble the following:<product name or component>-<KB article number>-<build number optional>-<version optional>-<architecture Identifier>-<language code optional>.exe
Extracted feature pack name schema
Once a software update package for a feature pack has been downloaded and extracted, the file name will resemble the following:[feature pack file name].msi
- ProductName This is the full product name, which includes the product version information. For SQL Server, this attribute could be one of the following:
- SQLServer2005
SQL Server 2005 - SQLServer2008
SQL Server 2008 - SQLServer2008R2
SQL Server 2008 R2
- SQLServer2005
- 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 Release The 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.
- 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 mapping
The 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 | SQLServer2008- KBxxxxxxx-Arch.exe |
| CU Package for SQL Server 2008 R2 | SQLServer2008R2_RTM_CUxx_kbxxxxxx_10_50_xxxx_Arch | SQLServer2008R2-KBxxxxxxx-Arch.exe |
| CU Package for SQL Server 2012 R2 | SQLServer2012_RTM_CUxx_kbxxxxxx_11_00_xxxx_Arch | SQLServer2012-KBxxxxxxx-Arch.exe |
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 | sqlncli.msi |
| SQL Writer | 2005_SPx_SQLWriter_CUxx_kbxxxxxx_9_00_xxxx_Arch | SQLWriter.msi |
| 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 | SQLServer2008_ASOLEDB10.msi |
| AS OLE DB for SQL Server 2012 | 2012_RTM_ASOLEDB_CUxx_kbxxxxxx_11_00_xxxx_Arch | SQL_AS_OLEDB.msi |
| ADMOMD.net | 2005_SPx_ADMOMD_CUxx_kbxxxxxx_9_00_xxxx_Arch | SQLServer2005_ADOMD.msi |
| 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 | SharedManagementObjects.msi |
| 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 | ReportBuilder3.msi |
| Sap BI | 2008_RTM_SapBI_CUxx_kbxxxxxx_10_00_xxxx_Arch | SapBI.msi |
| Stream Insight | 2008R2_RTM_StrmNsght_CUxx_KBxxxxx_10_50_xxxx_arch | StreamInsightClient.msi |
| Synchronization | 2008R2_RTM_Synch_CUxx_KBxxxxx_10_50_xxxx_arch | Synchronization.msi |
| PowerPivot for Excel Client | 2008R2_RTM_PPExcel_CUxx_KBxxxxx_10_50_xxxx_arch | PowerPivot_for_Excel_x86.msi |
| Stream Insight and Server | 2008R2_RTM_PPServer_CUxx_KBxxxxx_10_50_xxxx_arch | StreamInsight.msi |
| 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 | DACFramework.msi |
| ADOMD.NET | 2012_RTM_ADMOMD_CUxx_kbxxxxxx_11_00_xxxx_Arch | SQL_AS_ADOMD.msi |
| LocalDB | 2012_RTM_LocalDB_CUxx_KBxxxxx_11_00_xxxx_arch | SqlLocalDB.msi |
| Transact-SQL Language Service | 2012_RTM_TSQLLAN_CUxx_KBxxxxx_11_00_xxxx_arch | TSqlLanguageService.msi |
Best practices As a best practice, consider providing a name that you can use to easily identify packages during downloads.
Package descriptions
This 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 package
File nameSQLServer2005-KBxxxxxxx-Arch-Lang.exe (For SQL Server 2005)
SQLServer2008-KBxxxxxxx-Arch.exe (For SQL Server 2008)
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 Client
File namesqlncli.msi (For SQL Server 2005, 2008, 2008 R2, 2012)
Purpose Microsoft SQL Server Native Client is a single dynamic-link library (DLL) containing both the SQL OLE DB provider and SQL ODBC driver. It contains run-time support for applications using native-code APIs (ODBC, OLE DB and ADO) to connect to Microsoft SQL Server. SQL Server Native Client should be used to create new applications or enhance existing applications that need to take advantage of new SQL Server features. This installer for SQL Server Native Client installs the client components needed during run time to take advantage of new SQL Server features, and optionally installs the header files needed to develop an application that uses the SQL Server Native Client API.
Report builder
File nameReportBuilder.msi (For SQL Server 2008)
ReportBuilder3.msi (For SQL Server 2008 R2)
Purpose Report Builder provides an intuitive report authoring environment for business and power users with a Microsoft Office look and feel. Report Builder supports the full capabilities of Report Definition Language (RDL) including flexible data layout, data visualizations, and richly formatted text features of SQL Server Reporting Services. The download provides a stand-alone installer for Report Builder.
Report Builder Click Once
File nameRB2ClickOnce.msi (For SQL Server 2008, SQL Server 2008 R2)
Purpose The Click Once version of Report Builder designed to be started from Report Manager or a SharePoint library.
Reporting Services for SharePoint
File nameSharePointRS.msi (For SQL Server 2005)
rsSharePoint.msi (For SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012)
Purpose Microsoft SQL Server Reporting Services Add-in for SharePoint Technologies allows you to take advantage of SQL Server 2005 and 2008 report processing and management capabilities in SharePoint. The download provides a Report Viewer web part, web application pages, and support for using standard Windows SharePoint Services.
SQL Writer
File nameSQLWriter.msi (For SQL Server 2005)
Purpose The SQL Writer Service provides added functionality for backup and restore of SQL Server through the Volume Shadow Copy Service framework. When running, Database Engine locks and has exclusive access to the data files. When the SQL Writer Service is not running, backup programs running in Windows do not have access to the data files, and backups must be performed using SQL Server backup. Use the SQL Writer Service to permit Windows backup programs to copy SQL Server data files while SQL Server is running.
AS OLE DB
File nameSQLServer2005_ASOLEDB9.msi (For SQL Server 2005)
SQLServer2008_ASOLEDB10.msi (For SQL Server 2008 and SQL Server 2008 R2)
SQL_AS_OLEDB.msi (For SQL Server 2012)
Purpose The Analysis Services OLE DB Provider is a COM component that software developers can use to create client-side applications that browse metadata and query data stored in Microsoft SQL Server Analysis Services. This provider implements both the OLE DB specification and the specification’s extensions for online analytical processing (OLAP) and data mining. Note: Microsoft SQL Server Analysis Services OLE DB Provider requires Microsoft Core XML Services (MSXML) 6.0.
XMO/SMO (Shared Management Objects)
File nameSQLServer2005_XMO.msi (For SQL Server 2005)
SharedManagementObjects.msi (For SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012)
Purpose The Management Objects Collection package includes several key elements of the SQL Server 2005 management API, including Analysis Management Objects (AMO), Replication Management Objects (RMO), and SQL Server Management Objects (SMO). Developers and DBAs can use these components to programmatically manage SQL Server 2005. Note: Microsoft SQL Server Management Objects Collection requires Microsoft Core XML Services (MSXML) 6.0 and Microsoft SQL Server Native Client.
ADMOMD.net
File nameSQLServer2005_ADOMD.msi (For SQL Server 2005)
Purpose ADOMD.NET is a Microsoft .NET Framework object model that enables software developers to create client-side applications that browse metadata and query data stored in Microsoft SQL Server 2005 Analysis Services. ADOMD.NET is a Microsoft ADO.NET provider with enhancements for online analytical processing (OLAP) and data mining.
SapBI
File nameSapBI.msi (For SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012)
Purpose The Microsoft Connector for SAP BI is a set of managed components for transferring data to or from an SAP NetWeaver BI version 7.0 System. The component is designed to be used with the Enterprise and Developer editions of SQL Server 2008 or 2008 R2 Integration Services. To install the component, run the platform-specific installer for x86, x64, or Itanium computers respectively. For more information see the Readme and the installation topic in the Help file.
Stream Insight (client)
File nameStreamInsightClient.msi (For SQL 2008 R2 and SQL Server 2012)
Purpose For current users of StreamInsight, a run time data aggregator. StreamInsight allows software developers to create innovative solutions in the domain of Complex Event Processing that satisfy these needs. It allows to monitor, mine, and develop insights from continuous unbounded data streams and correlate constantly changing events with rich payloads in near real time. Industry specific solution developers (ISVs) and developers of custom applications have the opportunity to innovate on and utilize proven, flexible, and familiar Microsoft technology and rely on existing development skills when using the StreamInsight platform.
Stream Insight (Server)
File name
StreamInsight.msi (For SQL Server 2008 R2 and SQL Server 2012)
Purpose StreamInsight allows software developers to create innovative solutions in the domain of Complex Event Processing that satisfy these needs. It allows to monitor, mine, and develop insights from continuous unbounded data streams and correlate constantly changing events with rich payloads in near real time. Industry specific solution developers (ISVs) and developers of custom applications have the opportunity to innovate on and utilize proven, flexible, and familiar Microsoft technology and rely on existing development skills when using the StreamInsight platform.
Synchronization
File name
Synchronization.msi (For SQL 2008 R2)
Purpose Microsoft Sync Framework is a comprehensive synchronization platform that enables collaboration and offline access for applications, services and devices. Using Microsoft Sync Framework runtime, developers can build sync ecosystems that integrate any application, with any data from any store using any protocol over any network. Sync Services for ADO.NET is a part of the Microsoft Sync Framework (MSF). Sync Services for ADO.NET enables synchronization between ADO.NET enabled databases. Because Sync Services for ADO.NET is part of the MSF, any database that uses Sync Services for ADO.NET can then also exchange information with other data sources that are supported by MSF, such as web services, file systems or custom data stores. For more information about the Microsoft Sync Framework, please go to Microsoft Sync Framework Developer Center.
PowerPivot Excel Client
File name
PowerPivot_for_Excel_x86.msi (For SQL Server 2008 R2 and SQL Server 2012)
Purpose Microsoft® PowerPivot for Microsoft® Excel 2010 is a data analysis tool that delivers unmatched computational power directly within the software users already know and love — Microsoft® Excel. You can transform mass quantities of data with incredible speed into meaningful information to get the answers you need in seconds. You can effortlessly share your findings with others.
Master Data Services
Filename
MasterDataServices.msi (For SQL 2008 R2)
Purpose Master Data Services helps enterprises standardize the data people rely on to make critical business decisions. With Master Data Services, IT organizations can centrally manage critical data assets companywide and across diverse systems, enable more people to securely manage master data directly, and ensure the integrity of information over time.
Data-Tier Application Framework
Filename
DACFramework.msi (For SQL Server 2008 R2 and SQL Server 2012)
Purpose The SQL Server Data-tier Application (DAC) framework is a component that is based on the .NET Framework and that provides application lifecycle services for database development and management. Application lifecycle services include extract, build, deploy, upgrade, import, and export for data-tier applications in SQL Azure, SQL Server 2012, SQL Server 2008 R2, SQL Server 2008, and SQL Server 2005 through SQL Server Data Tools and SQL Server Management Studio. OLEDB Provider for DB2
Filename
DB2OLEDB.msi (For SQL Server 2008 R2)
DB2OLEDBV4.msi (For SQL Server 2012)
Purpose The Microsoft OLE DB Provider for DB2 v4.0 offers a set of technologies and tools for integrating vital data that is stored in IBM DB2 databases with new solutions. SQL Server developers and administrators can use the data provider with Integration Services, Analysis Services, Replication, Reporting Services, and Distributed Query Processor. LocalDB
Filename
SqlLocalDB.msi (For SQL Server 2012)
Purpose New to the SQL Server Express family, LocalDB is a lightweight version of Express that has the same programmability features, but it runs in user mode and has a fast, zero-configuration installation and a short list of prerequisites. Use this if you need a simple way to create and work with databases from code. Express can be bundled with Visual Studio, other Database Development tools or embedded with an application that needs local databases. Transact-SQL Language Service
Filename
TSqlLanguageService.msi (For SQL Server 2012)
Purpose The SQL Server Transact-SQL Language Service is a component that is based on the .NET Framework. This component provides parsing validation and IntelliSense services for Transact-SQL for SQL Server 2012, for SQL Server 2008 R2, and for SQL Server 2008.
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.
No comments:
Post a Comment