![]() ![]() To determine the version of SQL Server Analysis Services, use one of the following methods: The version of SQL Server Integration Services aligns with the version of SQL server that you had installed. The version of SQL Server Reporting Services (SSRS) is displayed on the Reporting Services Web Service URL, for example: The version is also displayed in the Reporting Services Configuration tool. For additional information about various versions of the tool, review Release notes for SQL Server Management Studio (SSMS).įor additional information about SQL Server Data Tools, review Download SQL Server Data Tools (SSDT) for Visual Studio. Starting with SQL Server 2016, SQL Server management studio is offered as a separate download. To determine which versions of the client tools are installed on your system, start Management Studio, and then click About on the Help menu. Original product version: SQL Server Original KB number: 321185 Determine the version of SQL Server Client tools If you ever need to find out exactly what build and service pack or CU you might have installed, you can always use for a comprehensive list.įor more information about blog posts, concepts and definitions, further explanations, or questions you may have…please contact us at We will be happy to help! Leave a comment and feel free to track back to us.This article describes the procedures to determine the version information of SQL Server components and client tools. Of course I know you can always just open the SQL Configuration Manager to find things but then I would not have had the fun of making a cool query would I?! It does not tell you if the instances are actually running or not so there is still some investigation to be done. This only gives a list of the instances found in the registry. UPDATE #AllInstanceOnMachine SET VersionFound = (SELECT VersionFound FROM #CurVer) WHERE InstName = Close and deallocate the cursorĪnd, here are the results from one of our dev servers. INSERT INTO #CurVer (RegValue, VersionFound) SET = N'Software\Microsoft\Microsoft SQL TABLE #CurVer SELECT InstName, RegPathToUse FROM #AllInstanceOnMachineįETCH NEXT FROM InstCur INTO < 0 BREAK INSERT INTO #AllInstanceOnMachine (InstName, RegPathToUse)ĮXEC = N'SOFTWARE\\Microsoft\\Microsoft SQL Server\\Instance Names\\SQL' ![]() DECLARE NVARCHAR(128)ĬREATE TABLE #AllInstanceOnMachine (InstName VARCHAR(128), RegPathToUse VARCHAR(128), VersionFound VARCHAR(50))ĬREATE TABLE #CurVer (RegValue VARCHAR(128), VersionFound VARCHAR(50)) Both will read values from the registry in the key values you point them at. My query uses xp_regread and xp_instance_regnumvalues. Now that I have stated that, the other obvious statement is that undocumented procedures can be pretty handy for some things, just use them with caution. This is because they can change or be removed at any time. Undocumented procedures from Microsoft are not supported and should not be used for regular production work. ![]() I found that this kind of information can be found in the registry which is accessible via a couple of undocumented extended procedures. Since I am working on a set of scripts that we can use for discovery on new systems, I thought it would be handy to have a query that would give me a list of SQL instances with the version that are installed. Many times shops many not be fully aware if additional instances are or have been installed on their server. It is pretty common that I frequently am asked to take over a server with SQL on it sight unseen. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |