Showing posts with label sqlserver servicepack. Show all posts
Showing posts with label sqlserver servicepack. Show all posts

Monday, October 5, 2015

How to Uninstall a SQL Server Service Pack


Uninstalling a SQL Server Service Pack





Did you know that starting with service packs (Service Pack 1) in SQL Server 2008 you can uninstall them from Add/Remove Programs like any other update?


image
But as always, backup both your user and system databases before applying any update, hot fix, cumulative update, or service pack!


If you are still using SQL Server 2005 or older, you have to use the manual method detailed here:
HOW TO: Remove a SQL Server Service Pack http://support.microsoft.com/kb/314823


================================================================

HOW TO: Remove a SQL Server 2005 or older Service Pack



SUMMARY
This step-by-step article describes how to remove a SQL Server service pack and expands on the information contained in the Readme.txt file for each service pack. 

When you install a new service pack, the service pack makes changes to the system tables for maintenance reasons, and upgrades user and distribution databases that are members of a replication topology. Due to these changes, you cannot easily remove service packs. There is no automated way to remove a service pack, and the process of removing a service pack involves several manual steps and risks if not done correctly.

Backup of System Databases

To remove the new service pack and revert to the build you were running before, you must have a backup of themaster, msdb, and model databases from the earlier build to which you want to revert. For example, to revert to the SQL Server 2000 pre-Service Pack 2 (SP2) version of SQL Server 2000 components, you must have a backup of themaster, msdb, and model databases prior to the SQL Server 2000 Service Pack 2 installation. If you do not have backups of your system databases on the service pack version to which you want to revert, you must perform the following steps to save your scheduled tasks, Data Transformation Services (DTS) packages, logins and full-text catalogs:
  • Script all scheduled tasks (that is, jobs, alerts and operators).
  • Save DTS packages to a file. You must save each package one by one into separate files.
  • Script the logins and passwords.
  • Back up the full-text catalog folders.
For additional information about how to script scheduled tasks and how to save DTS packages, click the article number below to view the article in the Microsoft Knowledge Base:
314546 HOW TO: Move Databases Between Computers that are Running SQL Server
For additional information about how to script the logins and password, click the following article number to view the article in the Microsoft Knowledge Base:
246133 HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
For additional information about backups of full-text catalogs, click the article number below to view the article in the Microsoft Knowledge Base:
240867 INF: How to Move, Copy, and Back Up Full-Text Catalog Folders and Files
NOTE: If you do not perform the preceding steps, you must manually re-create the scheduled tasks, DTS packages, logins and full-text catalogs.

back to the top

Use the following steps to remove the service pack and revert to a prior build:
  1. Detach all user databases. For more information, see the "Attaching and Detaching Databases" topic in Microsoft SQL Server 7.0 Books Online or the "How to attach and detach a database (Enterprise Manager)" topic in Microsoft SQL Server 2000 Books Online. 

    NOTE: If any of the databases are involved in replication, you must first disable publishing and distribution. For more information, see the "Disabling Publishing and Distribution" topic in SQL Server Books Online.
  2. Stop all SQL Server services (that is, MSSQLServer, SQLServerAgent, Microsoft Distributed Transaction Coordinator [MS-DTC], Microsoft Search).
  3. As a safety factor, copy the Data folder to a safe location. If you have data and log files in a separate folder other than the default Data folder, also copy those files.
  4. Uninstall SQL Server by using the Add/Remove Programs applet in Control Panel. After you remove SQL Server from the computer, Microsoft recommends that you restart your computer to remove files that were in use during the uninstall process.
  5. Install SQL Server with same character set, sort order, collation and destination folder for program and data files as that of the original installation.
  6. Apply any service pack that you might have been running before you installed the new service pack. For example, if you want to remove SQL Server 2000 SP2 and you were running SQL Server 2000 SP1 before you installed SQL Server 2000 SP2, then install SQL Server 2000 SP1.
  7. Restore the master, msdb, and model databases from backup if you have backups that match the version of service pack to which you want to revert. This automatically attaches any user databases that were attached when you created the backup. Attach any user databases that were created after the last backup of the masterdatabase. 

    If you do not have backups of the master, msdb and model databases then: 

    • Run the scripts that you created to re-create the logins and scheduled tasks (that is, jobs, alerts and operators). If you did not create the scripts before you uninstalled SQL Server, then re-create the logins and scheduled tasks manually.
    • Open the DTS packages you saved as files. Save the packages to SQL Server. For more information, see the "How to save a DTS package to SQL Server" topic in SQL Server 7.0 Books Online or the "Saving a DTS Package" topic in SQL Server 2000 Books Online.
    • Re-create any changes you want in the model database.
    • Attach all your user databases.
    NOTE: After you re-create the logins and passwords, your users may not be able to access the database because the users in the database may not be linked to the corresponding login. This problem is referred to as "Orphaned Users." To correct orphaned users, see step 3 in the following Microsoft Knowledge Base article:
    314546 HOW TO: Move Databases Between Computers that are Running SQL Server
  8. If you had full-text catalogs, restore the full-text catalogs and resynchronize the full-text catalogs. For more information, see the following article in the Microsoft Knowledge Base article:
    240867 INF: How to Move, Copy, and Back Up Full-Text Catalog Folders and Files
  9. If you use replication you must reconfigure replication manually.
  10. If you use SQL Mail, reconfigure SQL Mail. For more information, see the following article in the Microsoft Knowledge Base:
    263556 INF: How to Configure SQL Mail


Posted by at No comments:
Labels:

Friday, October 2, 2015

Best Practices for installing SQL Server service packs, hotfixes, cumulative updates

Best Practices for installing SQL Server service packs, hotfixes, cumulative updates


Best practices for installing service packs, cumulative updates and hotfixes for SQL Server

  1. Test on a test/dev SQL Server first and only after you have confirmed that all applications are working as expected then install it on a production SQL Server.
  2. Review the Readme for Service Pack/cumulative update/hotfix. Any concerns/recommendations will be found in the readme.
  3. Run DBCC CHECKDB on ALL databases (user and system databases) and ensure that there were no errors reported.
  4. Backup ALL databases (user and system databases) and full-text catalogs (if applicable). This is NOT required but highly recommended.
  5. Stop Monitoring and Anti-virus services
  6. Make sure you have the proper permissions to install (administrative privilege on server/cluster node)
  7. The below points are for clustered SQL Server instance
    • Make sure ALL SQL resources come online on ALL cluster nodes
    • Make sure that ALL disk resources (even the ones that not being used by SQL Server) are online and not in failed state.
    • Verify that there are no dependencies other than those created by the SQL Server setup on any SQL Server cluster resources.
    • Run MPSRPT_SQL.exe on all cluster nodes (not required but recommended)
    • Make sure all remote desktop connections are closed. You can connect to the node (you are running the setup from) using remote desktop connections but you should disconnect any remote connections to other cluster nodes.
Posted by at No comments:
Labels: ,

Tuesday, September 29, 2015

How to determine the version, edition, service pack of SQL Server and its components

How to determine the version of SQL Server


How to determine the edition of SQL Server & its components


How to determine the service pack of SQL Server


This article describes how to determine your current Microsoft SQL Server version number and the corresponding product or service pack level. It also describes how to determine the specific edition of SQL Server that you are using.
Notes
  • If you just need to know what a specific version number of SQL server maps to or the KB information for a specific cumulative update package or a service pack, refer to the More Information section of this article and search for the version number.
  • If you just want to find the latest builds for SQL Server, you can refer to the following article. Or, you can check the tables that correspond to your product in the More Information section of this article.

    957826 Where to find information about the latest SQL Server builds

How to determine the version of SQL Server Client tools

SQL Server Management Studio (SSMS)

To determine the version of the client tools that are installed on your system, start Management Studio, and then clickAbout on the Help menu. (The screen shot for this step is listed below).

The screen shot for this step

SQL Server Business Intelligence Development Studio (BIDS)

To check the version of Analysis Services Designer, of Integration Services Designer, or of SQL Server Reporting Services Designer, follow these steps:
  1. Under your SQL program group, start SQL Server Business Intelligence Development Studio.
  2. On the Help menu, click About.
  3. In the Installed products list, select the required component, and then notice the version that is given under theProduct details text box. 
    (The screen shot for this step is listed below).

    SQL Server 2005 / Visual Studio 2005

    The screen shot for this step for SQL Server 2005 / Visual Studio 2005


    SQL Server 2008 / SQL Server 2008 R2 / Visual Studio 2008

    The screen shot for this step for SQL Server 2008/ SQL Server 2008 R2 / Visual Studio 2008
Note For Business Intelligence features such as Integration Services, Reporting Services, and Analysis Services, you may have to install the latest service packs, cumulative updates, and hotfixes on the client-side computers to obtain the latest fixes while developing SSIS packages, SSRS reports, or Analysis Services cubes.

How to determine which version and edition of SQL Server Database Engine is running

To determine the version of SQL Server, you can use any of the following methods:

Method 1: Connect to the server by using Object Explorer in SQL Server Management Studio. After Object Explorer is connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of SQL Server.

Method 2: Look at the first few lines of the Errorlog file for that instance. By default, the error log is located at Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG and ERRORLOG.n files. The entries may resemble the following:
2011-03-27 22:31:33.50 Server      Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)                 Mar 29 2009 10:11:52                 Copyright (c) 1988-2008 Microsoft Corporation                Express Edition (64-bit) on Windows NT 6.1  (Build 7600: )
As you can see, this entry gives all the necessary information about the product, such as version, product level, 64-bit versus 32-bit, the edition of SQL Server, and the OS version on which SQL Server is running.

Method 3: Connect to the instance of SQL Server, and then run the following query:
Select @@version
An example of the output of this query is as follows:

Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)   Mar 29 2009 
10:11:52   Copyright (c) 1988-2008 Microsoft Corporation  Express 
Edition (64-bit) on Windows NT 6.1  (Build 7600: )

Method 4: Connect to the instance of SQL Server, and then run the following query:

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
Note This query works with any instance of SQL Server 2000 or of a later version.

The following results are returned:
  • The product version (for example, 10.0.1600.22)
  • The product level (for example, RTM)
  • The edition (for example, Enterprise)

For example, the results resemble the following.
10.0.1600.22RTMEnterprise Edition
Note The SERVERPROPERTY function returns individual properties that relate to the version information, although the@@VERSIONfunction combines the output into one string. If your application requires individual property strings, you can use the SERVERPROPERTY function to return them instead of parsing the @@VERSIONresults.

Method 5: Starting with SQL Server 2008, you can also use the Installed SQL Server Features Discovery report. This report can be found by locating the Tools page of SQL Server Installation Center. This tool gives information about all the instances of SQL Server that are installed on the system. These include client tools such as SQL Server Management Studio. The only thing to be aware of is that this tool can be run locally only on the system where SQL server is installed. It cannot be used to obtain information about remote servers. For more information, visit the following blog post on the Microsoft Developer Network (MSDN):
SQL Server 2008 Discovery Report
A snapshot of a sample report is as follows:

The screen shot showing a sample report

SQL Server 2014 version information

The following table lists the major releases of SQL Server 2014.
ReleaseProduct Version
SQL Server 2014 SP112.0.4100.1
SQL Server 2014 RTM12.0.2000.80
For more information information about the latest service packs for SQL Server 2014, click the following article number to view the article in the Microsoft Knowledge Base:
2958069 How to obtain the latest service pack for SQL Server 2014
For more information about the latest cumulative updates available for SQL Server 2014, click the following article number to view the article in the Microsoft Knowledge Base:
2936603 SQL Server 2014 build versions

SQL Server 2012 version information

The following table lists the major releases of SQL Server 2012.
ReleaseProduct Version
SQL Server 2012 Service Pack 211.0.5058.0
SQL Server 2012 Service Pack 111.00.3000.00
SQL Server 2012 RTM11.00.2100.60
For more information information about the latest service packs for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2755533 How to obtain the latest service pack for SQL Server 2012
For more information about the latest cumulative updates available for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
2983249 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 2 was released

SQL Server 2008 R2 version information

The following table lists the major releases of SQL Server 2008 R2.
ReleaseProduct version
SQL Server 2008 R2 Service Pack 310.50.6000.34
SQL Server 2008 R2 Service Pack 210.50.4000.0
SQL Server 2008 R2 Service Pack 110.50.2500.0
SQL Server 2008 R2 RTM10.50.1600.1
For more information information about the latest service packs for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2527041 How to obtain the latest service pack for SQL Server 2008 R2

For more information about the latest cumulative updates available for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

SQL Server 2008 version information

The following table lists the major releases of SQL Server 2008.
ReleaseProduct version
SQL Server 2008 Service Pack 410.00.6000.29
SQL Server 2008 Service Pack 310.00.5500.00
SQL Server 2008 Service Pack 210.00.4000.00
SQL Server 2008 Service Pack 110.00.2531.00
SQL Server 2008 RTM10.00.1600.22
For more information information about the latest service packs for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
968382 How to obtain the latest service pack for SQL Server 2008
For more information about the latest cumulative updates available for SQL Server 2008, click the following article numbers to view the articles in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
2629969 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

SQL Server 2005 version information

The following table lists the major releases of SQL Server 2005.
ReleaseProduct version
SQL Server 2005 Service Pack 49.00.5000.00
SQL Server 2005 Service Pack 39.00.4035
SQL Server 2005 Service Pack 29.00.3042
SQL Server 2005 Service Pack 19.00.2047
SQL Server 2005 RTM9.00.1399
For more information information about the latest service packs for SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005
sFor more information about the latest cumulative updates available for SQL Server 2005, click the following article number to view the article in the Microsoft Knowledge Base:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
2485757 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 4 was released

SQL Server 2000 version information

The following table lists version number of the Sqlservr.exe file.
ReleaseProduct version
SQL Server 2000 Service Pack 48.00.2039
SQL Server 2000 Service Pack 38.00.760
SQL Server 2000 Service Pack 28.00.534
SQL Server 2000 Service Pack 18.00.384
SQL Server 2000 RTM8.00.194
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack

SQL Server Reporting Services

To determine the version of SQL Server Reporting Services, refer to the following topic in SQL Server Books Online:
How to: Detect Version Information (Reporting Services)

SQL Server Integration Services

To determine the version of SQL Server Integration Services, refer to the following article in the Microsoft Knowledge Base:
942177 How to determine the version of SQL Server Integration Services

SQL Server Analysis Services

To determine the version of SQL Server Analysis Services, use one of the following methods:

Method 1: Connect to the server by using Object Explorer in SQL Server Management Studio. After Object Explorer is connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of Analysis Services.

Method 2: Check the version of the Msmdsrv.exe file in the Analysis Services bin folder. The default locations are shown in the following table.
Analysis Services versionLocation
2008 R2C:\Program Files\Microsoft SQL Server\MSAS10_50.InstanceName\OLAP\bin\MsMdSrv.exe
2008C:\Program Files\Microsoft SQL Server\MSAS10.InstanceName\OLAP\bin\MsMdSrv.exe
2005C:\Program Files\Microsoft SQL Server\MSSQL.n\OLAP\Bin\MsMdSrv.exe
2000C:\Program Files\Microsoft Analysis Services\Bin\MsMdSrv.exe

Method 3: Use the registry keys that are listed in the following table.
Analysis Services versionLocation
2008 R2HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10_50.InstanceName \MSSQLServer\CurrentVersion Key: CurrentVersion



HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10_50.InstanceName \Setup Keys: PatchLevel , Version, Key Edition
2008HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10.InstanceName\MSSQLServer\CurrentVersion Key: CurrentVersion



HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10.InstanceName \Setup\ Keys: PatchLevel, Version, Edition
2005HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.#\MSSQLServer\CurrentVersion Key: CurrentVersoin



HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.#\Setup Keys: PatchLevel, Version, Edition
2000HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\CurrentVersion Key: CSDVersion

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\Setup Key: PatchLevel

For more information, visit the following Microsoft TechNet blog post:
How to find Analysis Services Server Version

SQL Server replication

Because replication agents may be installed on several different computers, it is important to check the installed versions on all affected computers.

For example, the Distribution Agent in Transactional or Peer-to-Peer replication may exist on computers that differ from the publisher instance of SQL Server and may exist on the various subscriber instances of SQL Server in a pull subscription.

If you use Web Synchronization for Merge Replication or SQL Server 2000 Windows CE Edition replication, the IIS web server may not be the same computer as the computer that is running SQL Server. Therefore, you have replication agent files that are installed on the IIS web server. And you may have to check the version of those .dll files in the IIS virtual directory and update them explicitly to obtain the latest service packs, cumulative updates, and hotfixes for your web agents.

For more information, see the following topic in SQL Server Books Online:
Using Multiple Versions of SQL Server in a Replication Topology

Full-text search

Full-text search components include the following:
  • Sqlserver.exe
  • Sql_fulltext_keyfile.dll
  • Iftsph.dll
  • Fd.dll
  • Fdhost.exe
  • Fdlauncher.exe
Except for Sqlservr.exe, these components may not be updated with each cumulative update or service pack for the respective SQL Server product. The versions of these files will change only when there is a fix to the respective component. Generally, you can check the file version of each of these .dll files. The highest version in the list is the version of the full-text search component that is installed on the system.

You can use one of the following methods to determine the version of the full-text search component that is installed on your system.

Note Each of these methods may indicate that the version of the full-text search compnent is either RTM or a version that is earlier than the current version of the database component. We acknowledge that this is a problem and are working on fixing it in a future update.

Method 1: Check the version of SQL Server Full-Text Key (Sql_fulltext_keyfile.dll) in the SQL Server 2008 R2 or SQL Server 2008 installation folder. Typically, for SQL Server 2008 R2, this file is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\MSQL10_50.\MSSQL

For SQL Server 2008, this file typically is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\MSQL10.\MSSQL

Method 2: Check the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft sql server\Mssql10_50.instname\Setup\SQL_FULLTEXT_ADV
An example entry at this registry key is the following:
featurelist:          SQL_FullText_Adv=3 SQL_FullText_CNI=3ProductCode:    {9DFA5914-C275-42E0-810E-C88E46A7F9EA}Patchlevel: 10.50.1765.0Version: 10.50.1600.1
In this example entry, the third line (Patchlevel) indicates the current build of full-text search component that is installed, and the fourth line (Version) usually shows the original version of full-text search that is installed. In this case, it is SQL Server 2008 R2.

Method 3: Use the Summary.txt file that is created during setup. For SQL Server 2008 R2, this file is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\110\Setup Bootstrap\LOG\Summary.txt

For SQL Server 2008, this file is located in the following folder:
%ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\LOG\Summary.txt

See the following article in the Microsoft Knowledge Base for a known issue with full-text search components in SQL Server 2008 installations:
973888 The Full-Text Search component is not completely rolled back to the Service Pack 1 version after you uninstall Cumulative Update 3 for SQL Server 2008 Service Pack 1 that is applied by using a slipstream installation

SQL Server Master Data Services (MDS)

The MDS Configuration Manager does not show the currently installed version number directly.

Be aware that MDS has a unique versioning scenario in which the SQL Server database engine installation does not necessarily match the MDS version. The version may vary when you compare the SQL Server installation to the binaries deployed in the MDS website and the MDS catalog schema version. Manual steps that use the MDS Configuration Manager tool are required to update and to upgrade the MDS websites and database schemas. You can refer to the following blog post on hotfix and service pack update methodology for MDS:
Downloading and Installing SQL Server 2008 R2 Master Data Services (MDS) Cumulative Updates

The following registry key shows the binary versions that are installed on the SQL Server. However, this version does not necessarily match the website and database schema version until the MDS upgrade process is complete.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Master Data Services 10.5\CurrentVersion

You can check the installed product version and schema version by using the following query in the MDS catalog:
select * from mds.mdm.tblSystem

SQL Server Native Client

To determine the version of SQL Server Native Client, use one of the following methods:

Method 1: On the system where you want to find the version of Native Client, start the ODBC Administrator (odbcad32.exe), and then check the Version column under the Drivers tab.

Method 2: Check the following PatchLevel or Version keys at the following registry locations.
SQL version /
SQL Server Native Client version		Registry keys
SQL Server 2008 R2HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLNCLI10\CurrentVersion
SQL Server 2008 /
SQL Server Native Client 10		HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLNCLI10\CurrentVersion
SQL Server 2005 /
SQL Server Native Client 9		HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion
SQL Server 2012HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLNCLI11\CurrentVersion 

SQL Server Browser

The browser version should match the highest version of the SQL Server Database Engine and of the instances of Analysis Services that are installed on the computer.

SQL Server Writer

To determine the version of SQL Server Writer, check the following registry key value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SqlWriter\CurrentVersion
Keys: PatchLevel or Version

The Microsoft .NET Framework

To determine the version of the .NET Framework on your system, refer to the following article in the Microsoft Knowledge Base:
318785 How to determine which versions and service pack levels of the Microsoft .NET Framework are installed
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2027770 Understanding the .NET Framework requirements for various versions of SQL Server

SQL Azure

To find the version of your instance of SQL Azure and related information, see the following topic in Books Online:
SERVERPROPERTY (SQL Azure Database)

SQL Server CE

To find the version of your instance of SQL Server CE and related information, see the following resources:
More information

Frequently asked questions

Q1: How do you determine the version of SQL Server when SQL Server is not running?

A1: You can determine the version of SQL Server by using either method 2 or method 5 (for SQL Server 2008 or later versions) in the "How to determine which version of SQL Server Database Engine is running" section of this article.

Q2: How do I map the product versions to product names?

A2: You can use the following table as a reference.
Version patternSQL Product
12.0.x.xSQL Server 2014
11.0.x.xSQL Server 2012
10.50.x.xSQL Server 2008 R2
10.00.x.xSQL Server 2008
9.00.x.xSQL Server 2005
8.00.x.xSQL Server 2000

Frequently used terms and acronyms

Cumulative update (CU): A roll-up update that contains all previous critical on-demand hotfixes to date. Additionally, a CU contains fixes for issues that meet the hotfix acceptance criteria. These criteria may include the availability of a workaround, the effect on the customer, the reproducibility of the problem, the complexity of the code that must be changed, and other topics.

Hotfix: A single, cumulative package that includes one or more files that are used to address a problem in a product and are cumulative at the binary and file level. A hotfix addresses a specific customer situation and may not be distributed outside the customer's organization.

RTM: Usually means "release to manufacturing." In the context of a product such as SQL Server, it indicates that no service packs or hotfixes were applied to the product.

RTW: Usually means "release to web." It indicates a package that was released to the web and made available to customers for downloading.

Service pack: A tested, cumulative set of all hotfixes, security updates, critical updates, and updates. Service packs may also contain additional fixes for problems that are found internally since the release of the product and a limited number of customer-requested design changes or features.

For more information, visit the following websites:

SQL Server common build numbers and service packs

Note These tables use the following format and are ordered by the build number.
Build number or versionVersion description, (KB number for that update), release date

SQL Server 2014

Build number or versionVersion description, (KB number for that update), release date
12.0.4422.0SP1 CU #2 (3075950) August 17, 2015
12.0.4416.1SP1 CU #1 (3067839) June 19, 2015
12.0.4100.1SP1 RTW/PCU 1(3058865) May 4, 2015
12.0.2553.0RTM CU #9 (3075949) August 17, 2015
12.0.2546.0RTM CU #8 (3067836) June 19, 2015
12.0.2495.0RTM CU #7 (3046038) April 20, 2015
12.0.2480.0RTM CU #6 (3031047) February 16, 2015
12.0.2456.0RTM CU #5 (3011055) December 17, 2014
12.0.2430.0RTM CU #4 (2999197) October 21, 2014
12.0.2402.0RTM CU #3 (2984923) August 18, 2014
12.0.2370.0RTM CU #2 (2967546) June 27, 2014
12.0.2342.0RTM CU #1 (2931693) April 21, 2014
12.0.2000.8RTM – April 1, 2014

SQL Server 2012

Build number or versionVersion description, (KB number for that update), release date
11.0.5634.1SP2 CU #8 (3082561) September 21, 2015
11.0.5623.0SP2 CU #7 (3072100) July 20, 2015
11.0.5592.0SP2 CU #6 (3052468) May 18, 2015
11.0.5582.0SP2 CU #5 (3037255) March, 16, 2015
11.0.5569.0SP2 CU #4 (3007556) January 19, 2015
11.0.5556.0SP2 CU #3 (3002049) November 17, 2014
11.0.5548.0SP2 CU #2 (2983175) September 15, 2014
11.0.5532.0SP2 CU #1 (2976982) July 23, 2014
11.0.5058.0SP2 RTW/PCU 2(2958429), June 10, 2014
11.0.3482.00SP1 CU #13 (3002044) November 17, 2014
11.0.3470.00SP1 CU #12 (2991533) September 15, 2014
11.0.3449.00SP1 CU #11 (2975396) July 21, 2014
11.0.3431.00SP1 CU #10 (2954099) May 19, 2014
11.0.3412.00SP1 CU #9 (2931078) March 17, 2014
11.0.3401.00SP1 CU #8 (2917531) January 20, 2014
11.0.3393.00SP1 CU #7 (2894115) November 18, 2013
11.0.3381.00SP1 CU #6 (2874879) September 16, 2013
11.0.3373.00SP1 CU #5 (2861107) July 15, 2013
11.0.3368.00SP1 CU #4 (2833645) May 30, 2013
11.0.3349.00SP1 CU #3 (2812412) March 18, 2013
11.0.3339.00SP1 CU #2 (2790947) January 21, 2013
11.0.3321.00SP1 CU #1 (2765331) November 20, 2012
11.0.3000.00SP1 RTW/PCU 1(2674319), November 07, 2012
11.0.2424.00RTM CU #11 (2908007) December 16, 2013
11.0.2420.00RTM CU #10 (2891666) October 21, 2013
11.0.2419.00RTM CU #9 (2867319) August 20, 2013
11.0.2410.00RTM CU #8 (2844205) June 17, 2013
11.0.2405.00RTM CU #7 (2823247) April 15, 2013
11.0.2401.00RTM CU #6 (2728897) February 18, 2013
11.0.2395.00RTM CU #5 (2777772) Dec 17, 2012
11.0.2383.00RTM CU #4 (2758687) October 15, 2012
11.0.2332.00RTM CU #3 (2723749) August 31, 2012
11.0.2325.00RTM CU #2 (2703275) June 18, 2012
11.0.2316.00RTM CU #1 (2679368) April 12, 2012
11.0.2100.60RTM – March 6, 2012

SQL Server 2008 R2

Build number or versionVersion description, (KB number for that update), release date
10.50.4319.00SP2 CU #13 (2967540) June 30, 2014
10.50.4305.00SP2 CU #12 (2938478) April 21, 2014
10.50.4302.00SP2 CU #11 (2926028) February 18, 2014
10.50.4297.00SP2 CU #10 (2908087) December 17, 2013
10.50.4295.00SP2 CU #9 (2887606) October 28, 2013
10.50.4290.00SP2 CU #8 (2871401) August 22, 2013
10.50.4285.00SP2 CU #7 (2844090) June 17, 2013
10.50.4279.00SP2 CU #6 (2830140) April 15, 2013
10.50.4276.00SP2 CU #5 (2797460) February 18, 2013
10.50.4270.00SP2 CU #4 (2777358) Dec 17, 2012
10.50.4266.00SP2 CU #3 (2754552) October 15, 2012
10.50.4263.00SP2 CU #2 (2740411) August 31, 2012
10.50.4260.00SP2 CU #1 (2720425) July 24, 2012
10.50.4000.0SP2 RTW/PCU 2(2630458), July 26, 2012
10.50.2881.00SP1 CU #14 (2868244) August 8, 2013
10.50.2876.00SP1 CU #13 (2855792) June 17, 2013
10.50.2874.00SP1 CU #12 (2828727) April 15, 2013
10.50.2869.00SP1 CU #11 (2812683) February 18, 2013
10.50.2868.00SP1 CU #10 (2783135) Dec 17, 2012
10.50.2866.00SP1 CU #9 (2756574) October 15, 2012
10.50.2822.00SP1 CU #8 (2723743) August 31, 2012
10.50.2817.00SP1 CU #7 (2703282) June 18, 2012
10.50.2811.00SP1 CU #6 (2679367) Apr 16, 2012
10.50.2806.00SP1 CU #5 (2659694) Feb 22, 2012
10.50.2796.00SP1 CU #4 (2633146) Dec 19, 2011
10.50.2789.00SP1 CU #3 (2591748) Oct 17, 2011
10.50.2772.00SP1 CU #2 (2567714) Aug 15, 2011
10.50.2769.00SP1 CU #1 (2544793) Jul 18, 2011
10.50.2500.0SP1 RTW/PCU 1(2528583), July 12, 2011
10.50.1815.00RTM CU #13 (2679366) Apr 16, 2012
10.50.1810.00RTM CU #12 (2659692) Feb 21, 2012
10.50.1809.00RTM CU #11 (2633145) Dec 19, 2011
10.50.1807.00RTM CU #10 (2591746) Oct 17, 2011
10.50.1804.00RTM CU #9 (2567713) Aug 15, 2011
10.50.1797.00RTM CU #8 (2534352) June 20, 2011
10.50.1777.00RTM CU #7 (2507770) Apr 18, 2011
10.50.1765.00RTM CU #6 (2489376) Feb 21, 2011
10.50.1753.00RTM CU #5 (2438347) Dec 20, 2010
10.50.1746.00RTM CU #4 (2345451) Oct 18, 2010
10.50.1734.00RTM CU #3 (2261464) Aug 16, 2010
10.50.1720.00RTM CU #2 (2072493) Jun 21, 2010
10.50.1702.00RTM CU #1 (981355) May 18, 2010
10.50.1617.00GDR Security Update (2494088), June 21, 2011
10.50.1600.1RTM – May 10, 2010

SQL Server 2008

Build number or versionVersion description, (KB number for that update), release date
10.00.5850.00SP3 CU #15 (2923520) January 20, 2014
10.00.5848.00SP3 CU #14 (2893410) November 18, 2013
10.00.5846.00SP3 CU #13 (2880350) September 16, 2013
10.00.5844.00SP3 CU #12 (2863205) July 15, 2013
10.00.5840.00SP3 CU #11 (2834048) May 20, 2013
10.00.5835.00SP3 CU #10 (2814783) March 18, 2013
10.00.5829.00SP3 CU #9 (2799883) January 21, 2013
10.00.5828.00SP3 CU #8 (2771833) November 19, 2012
10.00.5794.00SP3 CU #7 (2738350) September 17, 2012
10.00.5788.00SP3 CU #6 (2715953) July 16, 2012
10.00.5785.00SP3 CU #5 (2696626) May 21, 2012
10.00.5775.00SP3 CU #4 (2673383) Mar 19, 2012
10.00.5770.00SP3 CU #3 (2648098) Jan 16, 2012
10.00.5768.00SP3 CU #2 (2633143) Nov 21, 2011
10.00.5766.00SP3 CU #1 (2617146) Oct 17, 2011
10.00.5500.00SP3 RTW / PCU 3 (2546951) Oct 6, 2011
10.00.4333.00SP2 CU #11 (2715951) July 16, 2012
10.00.4332.00SP2 CU #10 (2696625) May 21, 2012
10.00.4330.00SP2 CU #9 (2673382) Mar 19, 2012
10.00.4326.00SP2 CU #8 (2648096) Jan 16, 2012
10.00.4323.00SP2 CU #7 (2617148) Nov 21, 2011
10.00.4321.00SP2 CU #6 (2582285) Sep 19, 2011
10.00.4316.00SP2 CU #5 (2555408) Jul 18, 2011
10.00.4285.00SP2 CU #4 (2527180) May 16, 2011
10.00.4279.00SP2 CU #3 (2498535) Mar 17, 2011
10.00.4272.00SP2 CU #2 (2467239) Jan 17, 2011
10.00.4266.00SP2 CU #1 ( 2289254) Nov 15, 2010
10.00.4064.00GDR Security Update (2494089), June 14, 2011
10.00.4000.00SP2 RTW / PCU 2 (2285068) Sep 29, 2010
10.00.2850.0SP1 CU #16 (2582282) Sep 19, 2011
10.00.2847.0SP1 CU #15 (2555406) Jul 18, 2011
10.00.2821.00SP1 CU #14 (2527187) May 16, 2011
10.00.2816.00SP1 CU #13 (2497673) Mar 17, 2011
10.00.2808.00SP1 CU #12 (2467236) Jan 17, 2011
10.00.2804.00SP1 CU #11 (2413738) Nov 15, 2010
10.00.2799.00SP1 CU #10 (2279604) Sep 20, 2010
10.00.2789.00SP1 CU #9 (2083921) July 19, 2010
10.00.2775.00SP1 CU #8 (981702) May 17, 2010
10.00.2766.00SP1 CU #7 (979065) Mar 26, 2010
10.00.2757.00SP1 CU #6 (977443) Jan 18, 2010
10.00.2746.00SP1 CU #5 (975977) Nov 16, 2009
10.00.2734.00SP1 CU #4 (973602) Sep 21, 2009
10.00.2723.00SP1 CU #3 (971491) Jul 20, 2009
10.00.2714.00SP1 CU #2 (970315) May 18, 2009
10.00.2710.00SP1 CU #1 (969099) Apr 16, 2009
10.00.2573.00GDR Security update (2494096), June 14, 2011
10.00.2531.00SP1 RTW / PCU 1 April, 2009
10.00.1835.00RTM CU #10 (979064) Mar 15, 2010
10.00.1828.00RTM CU #9 (977444) Jan 18, 2010
10.00.1823.00RTM CU #8 (975976) Nov 16, 2009
10.00.1818.00RTM CU #7 (973601) Sep 21, 2009
10.00.1812.00RTM CU #6 (971490) Jul 20, 2009
10.00.1806.00RTM CU #5 (969531) May 18, 2009 SP1
10.00.1798.00RTM CU #4 (963036) Mar 16, 2009
10.00.1787.00RTM CU #3 (960484) Jan 19, 2009
10.00.1779.00RTM CU #2 (958186) Nov 19, 2008
10.00.1763.00RTM CU #1 (956717) Sept 22, 2008
10.00.1600.22RTM – Aug 6, 2008

SQL Server 2005

Build number or versionVersion description, (KB number for that update), release date
9.00.5266SP4 CU #3 (2507769) Mar 22, 2011
9.00.5259SP4 CU #2 (2489409) Feb 21, 2010
9.00.5254SP4 CU #1 (2464079) Dec 23, 2010
9.00.5000SP4 RTW (PCU4) Dec 16, 2010
9.00.4325SP3 CU #15 (2507766) Mar 22 , 2011
9.00.4317SP3 CU #14 (2489375) Feb 21, 2011
9.00.4315SP3 CU #13 (2438344) Dec 20, 2010
9.00.4311SP3 CU #12 (2345449) Oct 18, 2010SP3
9.00.4309SP3 CU #11 (2258854) Aug 16, 2010
9.00.4305SP3 CU #10 (983329) Jun 21, 2010
9.00.4294SP3 CU #9 (980176) Apr 19, 2010
9.00.4285SP3 CU #8 (978915) Feb 16, 2010
9.00.4273SP3 CU #7 (976951) Dec 21, 2009
9.00.4266SP3 CU #6 (974648) Oct 19, 2009
9.00.4230SP3 CU #5 (972511) Aug 17, 2009
9.00.4226SP3 CU #4 (970279) June 15, 2009
9.00.4220SP3 CU #3 (967909) Apr 20, 2009
9.00.4211SP3 CU #2 (961930) Feb 16, 2009
9.00.4207SP3 CU #1 (959195) Dec 19, 2008
9.00.4053Security update (970892) Oct 12, 2009
9.00.4035SP3 RTW (955706) Dec 15, 2008
9.00.3356SP2 CU #17 (976952) Dec 21, 2009
9.00.3355SP2 CU #16 (974647) Oct 19, 2009
9.00.3330SP2 CU #15 (972510) Aug 17, 2009
9.00.3328SP2 CU #14 (970278) June 15, 2009
9.00.3325SP2 CU #13 (967908) Apr 20, 2009
9.00.3315SP2 CU #12 (960485) Feb 16, 2009
9.00.3301SP2 CU #11 (958735) Dec 15, 2008
9.00.3294SP2 CU #10 (956854) Oct 21, 2008
9.00.3282SP2 CU #9 (953752) Aug 18, 2008
9.00.3257SP2 CU #8 (951217) Jun 16, 2008
9.00.3239SP2 CU #7 (949095) Apr 14, 2008
9.00.3228SP2 CU #6 (946608) Feb 18, 2008
9.00.3215SP2 CU #5 (943656) Dec 17, 2007
9.00.3200SP2 CU #4 (941450) Oct 15, 2007
9.00.3186SP2 CU #3 (939537) Aug 20, 2007
9.00.3175SP2 CU #2 (936305) June 18, 2007
9.00.3161SP2 CU #1 (935356) April 16, 2007
9.00.3152SP2 Rollup (933097) May 15, 2007
9.00.3068Security update (948109) Jul 8, 2008
9.00.3042SP2 (937137)
9.00.2047SP1
9.00.1399RTM

SQL Server 2000

Build number or versionVersion description, (KB number for that update), release date
8.00.2283Post-SP4 hotfix for MS09-004 (971524)
8.00.2282MS09-004: KB959420 October 29,2008
8.00.2273MS08-040 - KB 948111 July 8, 2008
8.00.2040Post-SP4 AWE fix (899761)
8.00.2039SQL Server 2000 SP4
8.00.1007Update.exe Hotfix Installer Baseline 2 (891640)
8.00.977Update.exe Hotfix Installer Baseline 1 (884856)
8.00.818(821277)
8.00.765Post SP3 hotfix rollup
8.00.760SQL Server 2000 SP3 or SP3a (8.00.766 ssnetlib.dll)
8.00.701Hotfix Installer v.1 released
8.00.534SQL Server 2000 SP2
8.00.384SQL Server 2000 SP1
8.00.194SQL Server 2000 RTM or MSDE 2.0

Older versions of SQL Server

SQL Server 7.0

Use the version number in the following table to identify the product or service pack level.
Version numberService pack
7.00.1063SQL Server 7.0 Service Pack 4
7.00.961SQL Server 7.0 Service Pack 3
7.00.842SQL Server 7.0 Service Pack 2
7.00.699SQL Server 7.0 Service Pack 1
7.00.623SQL Server 7.0 RTM

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
301511 How to obtain the latest SQL Server 7.0 service pack

SQL Server 6.5

Use the version number in the following table to identify the product or service pack level.
Version numberService pack
6.50.479SQL Server 6.5 Service Pack 5a Update
6.50.416SQL Server 6.5 Service Pack 5a
6.50.415SQL Server 6.5 Service Pack 5
6.50.281SQL Server 6.5 Service Pack 4
6.50.258SQL Server 6.5 Service Pack 3
6.50.240SQL Server 6.5 Service Pack 2
6.50.213SQL Server 6.5 Service Pack 1
6.50.201SQL Server 6.5 RTM

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
273914 Readme.txt for SQL Server 6.5 post-Service Pack 5a Update
Properties
Article ID: 321185 - Last Review: 09/22/2015 02:29:00 - Revision: 67.0

  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 64-bit Edition
  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft SQL Server 6.5 Standard Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Express Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Analysis Services
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Enterprise Evaluation
  • Microsoft SQL Server 2008 Express
  • Microsoft SQL Server 2008 Express with Advanced Services
  • Microsoft SQL Server 2008 Integration Services
  • Microsoft SQL Server 2008 R2 Analysis Services
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Express
  • Microsoft SQL Server 2008 R2 Express with Advanced Services
  • Microsoft SQL Server 2008 R2 Reporting Services
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Standard Edition for Small Business
  • Microsoft SQL Server 2008 R2 Web
  • Microsoft SQL Server 2008 R2 Workgroup
  • Microsoft SQL Server 2008 Reporting Services
  • Microsoft SQL Server 2008 Standard Edition for Small Business
  • Microsoft SQL Server 2008 Web
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Express
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Web
  • Microsoft SQL Server 2012 Business Intelligence
  • Microsoft SQL Server 2012 Enterprise Core
  • Microsoft SQL Server 2014 Business Intelligence
  • Microsoft SQL Server 2014 Developer
  • Microsoft SQL Server 2014 Enterprise
  • Microsoft SQL Server 2014 Enterprise Core
  • Microsoft SQL Server 2014 Express
  • Microsoft SQL Server 2014 Standard
  • Microsoft SQL Server 2014 Web
Reference:
https://support.microsoft.com/en-us/kb/321185
Posted by at No comments:
Labels: ,
Subscribe to: Posts (Atom)