Getting SQL Edition into PDQ Inventory

Comments

7 comments

  • Official comment
    Shane Corellian

    Howdy Ken,

    Try using a registry scanner. I don't have a lot of different editions of SQL Server to verify but with the new registry scanners (they were recently modified to allow wildcards in the path) this was a breeze.

    I created a new Scan Profile. I added a registry scanner and added the following filter under the HKEY_LOCAL_MACHINE hive.

    SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL*.MSSQLSERVER\Setup\Edition

     

    After creating the scan profile scan your machines that have SQL Server. Below are screenshots from a report showing the Columns and Filters tabs. This report returned the expected results. Please note I did add an extra filter to only report computers that had a service called MSSQLSERVER. You could probably remove that if you'd prefer.



     

    Comment actions Permalink
  • Trav A. Tonsfeldt

    Any Updates for this?

     

    0
    Comment actions Permalink
  • Shane Corellian

    Hi Trav,

    Did you try the steps listed above? You will need to utilize the registry scanning to pull the SQL edition.

    0
    Comment actions Permalink
  • Brad Dees

    I followed the steps above but made a couple minor tweaks for my desired results.  I wanted to include the express editions in the results.  

     

     

    0
    Comment actions Permalink
  • Trav A. Tonsfeldt

    I also made some tweaks had to use wildcards.  Is there any way to find the out if the Edition is core or uses CALs?

    0
    Comment actions Permalink
  • Shane Corellian

    Hi Trav,

    I don't know where to look to determine if CALs are used.

    0
    Comment actions Permalink
  • Ryan R. Bill

    Here is the scan profile that I setup to include an older version of SQL in our environment (SQL 2000), plus some 64-bit installs of SQL express:



    0
    Comment actions Permalink

Please sign in to leave a comment.