none
How to check edition of SSIS (no db engine)?

    Question

  • Is there a way to check the edition of SSIS? i've tried connecting to SSIS through SSMS and looking at the reports, but that just gives me the version number.

    there is no database so SELECT @@version doesn't apply. It's also possible to have different editions of sql db engine and SSIS installed on the same server so that's more of an inferred edition rather than the actual ssis edition. i want to find out from SSIS directly what edition it is


    Jakub @ Adelaide, Australia

    Wednesday, July 09, 2014 5:06 AM

Answers

  • You can try this:

    Use regedit to peek at the registry.

    Look for HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Microsoft SQL Server\{100|110, where 100 = SQL 2008{r2} and 110 = SQL 2012} \Tools\Setup\

    You will see the edition listed.

    • Marked as answer by jakubk Thursday, July 10, 2014 3:42 AM
    Thursday, July 10, 2014 3:33 AM

All replies

  • If you open  SSIS package check for About Microsoft Visual Studio under HELP menu.
    There you can find out the Version of SSIS

    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    Wednesday, July 09, 2014 6:59 AM
  • so i'd need to install BIDS/SSDT?

    Jakub @ Adelaide, Australia

    Wednesday, July 09, 2014 7:01 AM
  • and i dont mean the version, i mean the edition (STANDARD/ENTERPRISE/DEVELOPER etc)

    Jakub @ Adelaide, Australia

    Wednesday, July 09, 2014 7:01 AM
  • if SQL Server is also installed on that same machine you could use:

    SELECT SERVERPROPERTY ('edition'), SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel')

    (it's connected to SQL Server):


    Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com | Twitter



    Wednesday, July 09, 2014 3:45 PM
    Moderator
  • check if this article helps you

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;942177


    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

    Wednesday, July 09, 2014 3:54 PM
  • There is no such thing as an "edition" for SSIS. 

    Please see:

    http://support.microsoft.com/kb/321185

    Wednesday, July 09, 2014 3:57 PM
  • Hi,

    you can connect to ssis from ssms and right click to run general report.

    There you will find out version and build no of your installation.

    Regards

    Hope this helps.

    • Proposed as answer by kaushall_shah Wednesday, July 09, 2014 4:03 PM
    • Unproposed as answer by jakubk Wednesday, July 09, 2014 11:27 PM
    Wednesday, July 09, 2014 4:03 PM
  • There is no such thing as an "edition" for SSIS. 

    Please see:

    http://support.microsoft.com/kb/321185


    There are SQL Server editions that have effect on the transformations you can use. For example fuzzy logic requires Enterprise edition: http://sqlblog.com/blogs/andy_leonard/archive/2012/04/18/an-important-consideration-for-ssis-and-sql-server-2012-business-intelligence-edition.aspx

    Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com | Twitter

    Wednesday, July 09, 2014 4:15 PM
    Moderator
  • Hi all, thanks for all the replies! even the not so relevant ones..

    Tom,

    There is no such thing as an "edition" for SSIS. 

    Please see:

    http://support.microsoft.com/kb/321185

    The below error message seems to indicate there are

    the component is the oracle attinuity source connector

    And SSISJoost (first condolences, missed out yet again), and I've seen SSIS installed by itself with no db engine on the same machine. This is an approach i've seen done by proponents of the file system deployment and where they use a different method to orchestrate the packages (eg control-m or regular windows scheduler) instead of sql agent. How do I find the edition of SSIS in this case?

    It's how SSIS in SSDT/BIDS works. I never install the sql engine on my local dev machine, yet i'm able to execute a package either from within vistual studio, by double clicking the file (via dtexecui) or by invoking dtexec on the command line. Im assuming the SSIS edition is Developer in this case.


    Jakub @ Adelaide, Australia


    • Edited by jakubk Wednesday, July 09, 2014 11:41 PM sorry, the forum seems to shrink the image, can't find a way to make it maintain the original size
    Wednesday, July 09, 2014 11:40 PM
  • You can try this:

    Use regedit to peek at the registry.

    Look for HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Microsoft SQL Server\{100|110, where 100 = SQL 2008{r2} and 110 = SQL 2012} \Tools\Setup\

    You will see the edition listed.

    • Marked as answer by jakubk Thursday, July 10, 2014 3:42 AM
    Thursday, July 10, 2014 3:33 AM
  • brilliant, thanks.


    Jakub @ Adelaide, Australia

    Thursday, July 10, 2014 3:43 AM
  • That is actually a different question, "how do I know if the Advanced Transformations are installed"?

    That is a function of the media used to install the SSIS service.  As Ernest said, you can find that in the registry key.

    Thursday, July 10, 2014 12:36 PM
  • I have been puzzled by the same question. Though registry can be a good indicator, why cannot SSIS provide some direct information about its edition? For example, in my laptop, I can install both SQL Server 2008 R2 SSIS standard edition and SQL Server 2012 SSIS developer edition, this means I have to figure out which SSIS belongs which sql server engine (sql2k8 or sql2012) and then go to the corresponding registry path to figure it out. SSAS/SSRS and SQL server engine itself all have direct information about version and edition info.
    Saturday, February 14, 2015 6:27 AM