Microsoft SQL Server versions and editions

The purpose of this article is to describe how to identify your current Microsoft SQL Server version number and the corresponding product or service pack level. It also describes how to identify the specific edition of SQL Server you are using in your environment.

How to determine which version of SQL Server 2008 is running

To determine which version of Microsoft SQL Server 2008 is running, connect to SQL Server 2008 by using SQL Server Management Studio, and then run the following Transact-SQL statement.


SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

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.22 RTM Enterprise Edition

The following table lists the product version and file version (Sqlservr.exe) numbers for SQL Server 2008:


                               Product Version      File Version (SQLSERVR.EXE)

RTM                            10.0.1600.22         2007.100.1600.0
SQL Server 2008 Service Pack 1 10.0.2531.0          2007.100.2531.0

How to determine which version of SQL Server 2005 is running

To determine which version of Microsoft SQL Server 2005 is running, connect to SQL Server 2005 by using SQL Server Management Studio, and then run the following Transact-SQL statement.


SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

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

For example, the results resemble the following.

9.00.1399.06 RTM Enterprise Edition

The following table lists the product version and file version (Sqlservr.exe) numbers for SQL Server 2005:


                                       Product Version      File Version (SQLSERVR.EXE)

RTM                                    9.00.1399            2005.90.1399
SQL Server 2005 Service Pack 1         9.00.2047            2005.90.2047
SQL Server 2005 Service Pack 2         9.00.3042            2005.90.3042
SQL Server 2005 Service Pack 3         9.00.4035            2005.90.4035

How to determine which version of SQL Server 2000 is running

To determine which version of SQL Server 2000 is running, connect to SQL Server 2000 by using Query Analyzer, and then run the following code.


SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

The following results are returned:

The product version (for example, 8.00.534)
The product level (for example, "RTM" or "SP2")
The edition (for example, "Standard Edition").

For example, the results resemble the following:

8.00.534 SP2 Standard Edition

The following table lists the product version and file version (Sqlservr.exe) numbers for SQL Server 2000:


                                       Product Version      File Version (SQLSERVR.EXE)

RTM                                    8.00.194             2000.80.194.0
SQL Server 2000 SP1                    8.00.384             2000.80.384.0   
SQL Server 2000 SP2                    8.00.534             2000.80.534.0
SQL Server 2000 SP3                    8.00.760             2000.80.760.0
SQL Server 2000 SP3a                   8.00.760             2000.80.760.0
SQL Server 2000 SP4                    8.00.2039            2000.8.00.2039

For releases of SQL Server prior to SQL Server 2000, check Microsoft Support KB article 31185. Keep in mind also there were a number of Cumulative Updates for each version, which are not listed above. For a detail list of Cumulative Updates version information check SQL Team's article on SQL Server Versions.

Until next post!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Anonymous said…
Hi Mariano,

I have always used select @@version to get this information. Is there a difference?

Thanks,
-Victoria
May 22, 2009 at 7:33 AM
Mariano Gomez said…
Victoria,

The SERVERPROPERTY function returns individual properties that relate to the version information whereas the @@VERSION function 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 @@VERSION results.

MG.-
Mariano Gomez, MVP
http://www.maximumglobalbusiness.com
May 27, 2009 at 6:37 PM
Post a Comment

Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

Image
In this video, learn to enable Power Apps Application Monitoring with Azure Application Insights.  The following topics are covered in this video:  ( 0:00 ) - Intro  ( 0:36 ) - What is Azure Application Insights  ( 1:32 ) - The timesheet app  ( 2:12 ) - Creating an Application Insight for the timesheet application  ( 3:55 ) - Identify and copy the application instrumentation key  ( 4:09 ) - Enabling the timesheet application with the instrumentation key  ( 5:32 ) - Working with Application Insights  ( 8:06 ) - Outro For additional information on Azure Application Insights, please follow these resources: Microsoft Docs - What is Azure Application Insights? here Adam Marczak - Azure for Everyone: Azure Application Insights Tutorial, here To check out my YouTube channel visit: https://youtube.com/user/mgomezb1 LIKE AND SUBSCRIBE!!! Until next post! MG.- Mariano Gomez, MVP
Read more

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics
Read more

eConnect Integration Service for Microsoft Dynamics GP 2010

Image
One of the biggest improvements in eConnect 2010 is the addition of the new eConnect Integration Service . The eConnect installer now creates a new Windows Service application named eConnect for Microsoft Dynamics GP 2010 integration Service . The eConnect Integration Service is a Windows Communication Foundation (WCF) service that replaces the (very unstable) eConnect COM+ object available in previous versions of eConnect. The eConnect Integration Service supports the operations of the eConnect .NET assemblies, the BizTalk adapter, and MSMQ interfaces. In addition, you can use the service directly from an application that adds a service reference to the eConnect Integration Service. If you add a service reference, you do not need to add the Microsoft.Dynamics.GP.eConnect assembly and namespace to your development project. To add the eConnect Integration Service to an application, you must first add a service reference to the Visual Studio project for that application. To add a servi
Read more