Find the SQL Server Analysis Services and Reporting Services Version, Edition and Service Pack

Problem
I have a stand-alone instances of SQL Server Analysis Service (SSAS) and SQL Server Reporting Service (SSRS) running in my environment. Ho can I find hat the version and edition of each pac!age as ell as the Service "ac! installed# $hec! out this tip to learn more.

Solution
A fe months %ac! one of my colleagues as!ed me to investigate a particular server. &he machine as not actually hosting any data%ases' %ut running a single' stand-alone instance of SQL Server Analysis Service (SSAS)' much li!e the figure sho n %elo .

Her (uestion as simple enough) hat Service "ac! is running on this instance# *as it the latest version# If not' ere e running any of the $umulative +pdate ($+) pac!ages# ,o typically most installations of SQL Server Analysis Service (SSAS) or SQL Server Reporting Service (SSRS) ould see the service running along a default or named instance of the relational engine. &hat-s %ecause the ./As had chosen the data%ase engine as primary component and selected SSAS or SSRS as additional components during installation. It-s easy to chec! hat version and edition of the relational engine is running %y simply connecting to the data%ase engine from SQL Server 0anagement Studio and %ringing up the "roperties indo (or (uerying the 1123RSI4, glo%al varia%le). 5inding the Service "ac! level is also fairly easy) 6ust go to the SQL Server $onfiguration 0anager application' %ring up the "roperties indo of the data%ase service and chec! the Advanced ta%. It ould %e fair to assume the Service "ac! applied to the data%ase engine ould also %e applied to SSAS or SSRS. ,ot in this case though. I could connect to the SSAS instance from 0anagement Studio' %ut there as no entry in the "roperties indo that could sho me the Service "ac!. I !ne the machine as running 7889 R7 Analysis Service' %ut had no idea a%out the Service "ac!. :ou ould face the same pro%lem hen connecting to Reporting Service from 0anagement Studio.

Windows Registry Node for SSRS and SSAS Version and Edition 1

As I found later' the %est place to loo! for the version and edition information for SSAS and SSRS is actually the *indo s registry. &he registry !eeps all sorts of information a%out SQL Server components installed and this is here I found hat I as loo!ing for. &o start' here is here *indo s !eeps all SQL Server related information)

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server So the first step is to actually identify this node. All the other relevant nodes' !eys and values are nested underneath it. *e can find a fe things if e navigate further do n from here) &he ma6or release version of the product (788;' 7889' 7889 R7 or 78<7#) &he edition (Standard' 3nterprise' .eveloper' etc.) &he current version installed ( ithout any Service "ac!' $+ or hotfi=' this ill %e the same as the released version) &he Service "ac! Indication of any patches or hotfi=es installed on top of Service "ac! e e=pand to the follo ing path)

&o get this information'

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\ComponentNameVersion InstanceName ,ote the ComponentNameVersion InstanceName %it. &here are fe of) things to %e mindful

In SQL 788;' the component part ill %e called 0SSQL.n for SSAS or SSRS. n ill %e a num%er li!e 7 or >. &ypically hen %oth SSAS and SSRS are installed ith the data%ase engine' 4LA" service is designated 0SSQL.7 and Reporting Service 0SSQL.> and so on. In SQL 7889' 7889R7 or 78<7' the component ill %e called 0SAS for Analysis Service and 0SRS for Reporting Service &he version ill %e << for SQL 78<7' <8?;8 for SQL 7889 R7 and <8 for SQL 7889 Instance name ould either %e the actual name of the instance or 0SSQLS3R23R for a default instance

So if e are considering a SQL 7889 R7 system ith an Analysis Service instance called 4LA"' the registry node here e need to start navigating do n ill %e) HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSAS!"_#" OLA$ 5or a default instance of SQL Server 7889 Reporting Service' the node HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MS%S!" MSSQLSE%VE% ,o that e have identified the starting point' let-s e=plore further do n. ill %e)

Finding the Current Version of SSAS or SSRS in the Windows Registry

&his registry !ey sho s the actual ma6or release of the component installed (e.g. SQL Server 7889 @ S"> or SQL Server 7889 R7 @ S"< etc.). ,ote that this entry also reflects the Service "ac! installed ith the product. &o get this information' navigate to the follo ing) HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\ComponentNameVersion InstanceName\MSSQLServer\C&rrentVersion In the follo ing picture' e can see the $urrent2ersion of a SQL Server 788; Analysis Service system. It-s listed as A)88.;888.8 hich is SQL Server 788; @ S"B)

Similarly' the $urrent2ersion of the Reporting Service of another 788;-%ased system is sho n %elo . &his one has a $urrent2ersion of A.88.>8B7.88 hich is SQL 788; @ S"7)

&he figures %elo sho the $urrent2ersions of SQL Server 7889 and 7889 R7 Analysis Services and a SQL 7889 R7 Reporting Service)

So ho do you ma!e sense of this arcane num%er to a meaningful value# *ell' that-s pretty o%vious) if it is something starting ith A' it-s SQL 788;. <8.8 ould %e SQL 7889. <8.;8 ould %e SQL 7889 R7 and << ould %e SQL 78<7 (this is the latest version of SQL at the time of this riting). Service "ac!# &hat-s hat e ill see ne=t.

Find the SQL Ser er Edition! Pat"h Le el and Ser i"e Pa"#
&he ne=t registry node that contains relevant information is) HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\ComponentNameVersion InstanceName\Set&p Here' you can find the editions of the SQL Server components installed. &here ill %e t o registry !eys) E'ition and E'ition()pe' %oth of these sho the same information. 5or Service "ac!' loo! no further than the !ey called S$. 5inally' t o other !eys orth chec!ing ould %e Version and $atc* Leve+. *hen a Service "ac! has %een installed' the 2ersion !ey-s value ill not %e the same as that of $urrent2ersion. If no $umulative +pdates or Hotfi=es ere applied after the Service "ac!' the "atch Level and the 2ersion !eys ill sho the same value. 4ther ise the "atchLevel !ey ill al ays have a higher value than the 2ersion !ey. Cust so that it does not sound too confusing' let-s consider the follo ing figures) In the first one' this is a SQL Server 788; =DB %it 3nterprise 3dition Analysis Service installation. &he Service "ac! applied as S" B. Also' no $+ or Hotfi=es have %een applied after the S".

Similar information for a SQL 788; Reporting Service installation is sho n %elo . 4nly in this case' e !no a patch update has %een applied after S"7 as rolled out)

In the follo ing figure' a SQL Server 7889 Analysis Service is sho n. Here again' a $+ as applied after the S" ("atch Level different than the 2ersion !ey). If you search for the "atch Level' this is actually the $umulative +pdate 7 released after S"<.

&he follo ing figure sho s a named instance of Analysis Service. &he instance is called E4LA"E. &he "atch Level is different than the 2ersion' indicating a minor patch update)

A default instance of SQL 7889 R7 Analysis Service loo!s li!e this)

5inally' the same type of information a%out a SQL 7889 R7 Reporting Service)

Final Words
Hopefully 0icrosoft ill !eep this structure of version' edition and service pac! info ithin *indo s registry in future releases as ell. &he fact the info is availa%le from the Registry means it can also %e (ueried programmatically.

Ne$t Ste%s&
8

Learn more a%out the SQL Server @@VERSIO !"#ctio# Investigate the registry entries of some of your Analysis Service and Reporting Service systems. 5ind out more a%out SQL Server Hotfi=es' $umulative +pdates' 5eature "ac!s and Service "ac!s $ere. +nderstand a%out 0icrosoft SQL Server Soft are +pdate "ac!age naming schema and convention $ere. Read this article %y Shashan! "a ar a%out finding Analysis Service version info programmatically