SQL Server 2008 Management Studio (SSMS) displaying incorrect build number?
Posted by denglishbi on March 29, 2009
One way to verify the version of your SQL Server components like the database engine, Reporting Services (SSRS), Analysis Services (SSAS), and Integration Services (SSIS) is by connecting to the component with SQL Server Management Studio (SSMS). Once you connect to one of these components you will see the name of the component along with the version number information and your connection information. Here is an example of what you will see (not the SSRS and SSIS information):
In looking at this we can see that I have installed SQL Server 2008 CU3 (SQL Server 2008 Build List – 2520 is not listed, but that is for CTP SP1). The odd thing is that SSRS and SSIS state that I am running build number 1600 which is the RTM release… That is odd So how can I verify the version information for these two products or did I really install CU3 for just the database engine and SSAS?
There are quite a few ways to check out the build for both of these two products (and I won’t go into each option here). For SSRS if I take a look at the properties I will see this information:
And you can see that I am actually on the CU3 build and not RTM. So now for SSIS I can take a look at the actual version number of the MsDtsSrvr.exe file in the %programfiles%Microsoft SQL Server100DTSBinn directory, but I would see this:
So that doesn’t help out at all. Apparently this has not been updated since RTM…well then lets take a look at a file in the CU3 list that was updated for Integration Services like dtexec.exe. By doing so you will see this information:
There are other ways to check out your SSIS build number (How to determine the version of SQL Server 2005 Integration Services), but in my case the information displayed the RTM build until I verified a specific file that was updated like dtexec.exe.
So if this is annoying for you and you would like to see this corrected then please vote on this bug on the Microsoft Connect site – Incorrect Version (build) number in SSMS with SSRS and SSIS
And by the way, you need to be on at least CU3 if you are using SQL Server 2008 maintenance plans and do not have SSIS installed on the same server – FIX: Error message when you run a maintenance plan in SQL Server 2008: "The SQL Server Execute Package Utility requires Integration Services to be installed". So if you don’t want to install SSIS on your database engine server then make sure you install CU3 if you are planning on using maintenance plans
UPDATE (4/4/2009): I received two comments yesterday in regards to this bug from Microsoft on the Connect site. I am assuming this means Kilimanjaro? Or maybe SP2 (unless it will be part of SP1)…
UPDATE (4/5/2009): I guess it will be fixed in SP1…so I guess I will need to wait until the RTM of SP1 to see if this is the case or not. Here is the last comment I just got today from Microsoft:
Thank you for filing this bug.
To clarify, this bug should be fixed in Katmai PCU1 also called Katmai SP1. If you do not find this to be the case, please re-activate this issue or file a new bug in this regard.
Posted by Microsoft on 4/5/2009 at 7:24 PM
UPDATE (6/2/2009): This is still a bug with SQL Server 2008 SP1. Check out one of my more recent blog entries – SQL Server 2008 SP1 Available and Install Experience – build 2531.