Share via

Licensing SSIS on a server used for deploying code via Visual Studio and SSIS to a SQL Server production server running on another server

Leo van Mourik 20 Reputation points
2026-03-19T08:33:18.6333333+00:00

See subject. Is it allowed to use Visual Studio on a management server used by a developer to deploy code via SSIS integration to a SQL server production environment that runs on a different server or will the management server be regarded as a part of the production environment ? No end users who run the application that uses the SQL Server production database have access to the management server.

If so, then the next question is : Visual Studio includes the right to use SQL Server , so the SSIS integration does not need to bel licensed separately, right ?

SQL Server Integration Services
0 comments
Answer accepted by question author
  1. Lakshmi Narayana Garikapati 1,225 Reputation points Microsoft External Staff Moderator
    2026-03-19T10:23:59.59+00:00

    Hi Leo van Mourik,

    Yes, this scenario is allowed. A server used only as a management or development server (for example, running Visual Studio to develop and deploy SSIS packages) is not considered part of the production environment, as long as no SQL Server components are installed or executed on it. Licensing is required only on machines where SQL Server components (such as the Database Engine or the SSIS runtime) are actually installed and run. Since end users do not access the management server and SSIS packages execute only on the production SQL Server, only the production server needs to be licensed.

    Regarding Visual Studio: Visual Studio (any edition, including Community) can be used to design, build, and deploy SSIS packages without requiring a SQL Server license on that machine. However, Visual Studio does not include a SQL Server runtime license. SSIS itself is licensed as part of SQL Server and must be licensed only on the server where the SSIS runtime is installed and packages are executed. In short, developing and deploying SSIS from Visual Studio is fine without extra licensing, but running SSIS packages requires a properly licensed SQL Server on the execution server.

    https://learn.microsoft.com/en-us/sql/integration-services/integration-services-features-supported-by-the-editions-of-sql-server?view=sql-server-ver15
    https://learn.microsoft.com/en-us/answers/questions/1353955/licence-of-ssis

    Thanks,

    Lakshmi.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Yitzhak Khabinsky 27,101 Reputation points
    2026-03-19T18:46:24.9233333+00:00

    Hi @Leo van Mourik ,

    SSIS has a so called development environment. It needs two components to function correctly:

    SSIS development environment DOESN'T needs any SSIS pertaining license(s).

    SSIS run-time environment needs the following:

    • SQL Server instance with a database engine.
    • SQL Server SSIS component.
      Allows to create Integration Service Catalog, SSISDB database, etc.

    SSIS run-time environment does need SQL Server instance level license(s) just in a Production environment. You need to use SQL Server Standard or Enterprise editions for that.
    SSIS run-time environments such as Test and UAT don't need a license. You could use SQL Server Developer Edition for such environments.
    Also, there is no such thing as a separate SSIS only license.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.