What is the corect version for SQL Server 2012 SP1


  • All the Microsoft documentation says that SQL Server 2012 SP1 is version number 11.0.3000.00. But at a customer site (related to SCOM and grouping SQL Server) all their SP1 versions (Enterprise, Standard and Developer) were 11.1.3000.0 if
    SP1 was installed. RTM versions were the correct number.

    In the forum I have also seen some people mention that their version was 11.1.3000 so it is not just this organisation.

    Any idea on why their servers say a different number compared to the Microsoft documentation on their web site?

    Ian Blyth Cosiris - OpsMgr Blog -

    Thursday, September 12, 2013 10:58 AM

All replies

  • Hello ,

    Version of SQL server 2012 is 11.0.3000.00 and same can be confirmed from details section of below link.You should believe this site

    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    Thursday, September 12, 2013 11:25 AM
  • When I do select @@version


    Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)

                    Oct 19 2012 13:38:57

                    Copyright (c) Microsoft Corporation

                    Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)


    From SCOM Discovered Inventory


    Display Name sqlname Full Path Name servername\SCOMOPERATIONS Instance Name SCOMOPERATIONS Version 11.1.3000.0 Edition Standard Edition


    In Registry


    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\SQLServer2012\CurrentVersion

    it shows as 11.1.300.0.

    So the version is set wrong in the registry but that is what SCOM picks up. Although SQL itself returns the version documented.

    Ian Blyth Cosiris - OpsMgr Blog -

    Thursday, September 12, 2013 11:30 AM
  • Weird. I have the same in that registry key. The weird thing is that this key isn't instance specific, so how would SCOM report if you have say 2 instances of different build levels? Looks like two issues here: SCOM grabbing a wrong key, and SQL Server writing a weird version number in this key (whatever that key might be for).

    Tibor Karaszi, SQL Server MVP | web | blog

    Thursday, September 12, 2013 3:13 PM
  • I did a search on the registry for 11.1.3000 and it shows up in lots of keys (too many to list) for SQL (tools, reporting, analysis server etc) including each instance. For 11.0.3000 it only shows up in one key 



    Name = Microsoft.AnalysisServices,fileVersion="11.0.3000.0",version="",culture="neutral",publicKeyToken="89845DCD8080CC91",processorArchitecture="MSIL"

    So SCOM will search the registry using WMI and bring back the keys for each instance and as practically all the registry keys bring the "wrong" key back then this is what is used. The SQL Management Pack creates a group based on 11.0.* and so none of the SP1 servers are in that group.

    It might be easier to change the documentation to 11.1.3000. :-) 

    Ian Blyth Cosiris - OpsMgr Blog -

    Thursday, September 12, 2013 3:32 PM
  • How weird. On my machine, I have 11.0.3000.0 for, for instance, below two keys:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.K\MSSQLServer\CurrentVersion

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSRS11.K\MSSQLServer\CurrentVersion

    Tibor Karaszi, SQL Server MVP | web | blog

    Thursday, September 12, 2013 3:39 PM
  • Hello ,

    I have a SQL Server 2012 SP1 and to see the version , I am using the facets of the server ( because I am interested by SMO )

    I obtain :

    VersionString               ==> 11.0.3128.0

    ResourceVersionString  ==>11.00.3000

    ProductLevel                ==> SP1 


    Have a nice day

    Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

    Wednesday, September 25, 2013 12:08 PM