SSIS Runtime - free redistributable?

SSIS Runtime - free redistributable?

• Sudhendra

  Sure, the SSIS object model lets you run SSIS packages
  stored anywhere.
  
  But all you can do with it is load SSIS package from
  a remote server and then run it locally (consuming
  local CPU and memory) and thus I believe you need
  SSIS license for machine where they are executed.
  
  

• vln

  mat_net wrote:

  1. Is the SSIS runtime a free redistributable like in DTS 2000

  
  No. You need to install SSIS on any machine where you will be running packages. This requires a license.
  
  

  mat_net wrote:

  2. Can it be used to run a package where SQL Server 2005 is not installed ... e.g. on clients

  
  As above. N.B. The only pre-req is SSIS, not any other SQL Server component. Note that you can run packages in BIDS (the workstation dev tool) but obviously this wouldn't be used in a production environment. If you need to run packages from the command-line then you need SSIS runtime installed.
  
  

  mat_net wrote:

  3. Can the SSIS object model be used in a custom .NET application to execute packages stored on the server Is the runtime required in any way in that scenario...hope not.

  
  Yes, it is required as far as I know.
  
  

  mat_net wrote:

  Also does the usage of the Object Model require any sort of SQL Server licenses.

  
  Don't know. I expect not but don't quote me on that.
  
  HTH
  
  -Jamie
  
  

• Ichiro

  Thanks Michael.
  Idea of creating a SQL Server job (with dtexec cmds) on the server and using SMO to run the job remotely is good.
  
  Are you sure the object model cannot run SSIS packages stored on a server. I mean can't we just specify the remote instance name instead of localhost. Tried this   (For packages stored inside the SQL Server repository)
  
  Still waiting for a person from Microsoft to confirm the licensing queries.
  
  

• johnalexander

  I'll try to clarify the licensing positioning if I can. The basic principle is this: to run an SSIS package in production you need an appropriate SQL Server license wherever the package runs.

  With a tools-only install it is possible to run SSIS packages in the designer. But you are only licensed to use this for development not for production. In fact, it is not a suitable solution for production as it can not be run unattended.

  Using the object model, as Michael points out, you can load a package stored on a server. But it executes where your client application executes - and you must have an appropriate SQL Server license for that execution.

  Donald

  
  
  

• Rajeev2006

  Can we have a reply from a Microsoft person on this
  
  Thanks for the reply Jamie, but when you say a license is required for the runtime, what type of license is it device cal/user cal
  
  And can the SSIS object model in .NET be used to run a SSIS package stored on the server remotely

  
  
  

• richbrownesq

  mat_net wrote:

  And can the SSIS object model in .NET be used to run a SSIS package stored on the server remotely

  SSIS object model only allows to run packages locally, regardless of licensing issues. It does not have any method for executing packages on remote machine.

  The common way to remotely execute packages is create Agent Job that runs SSIS package on a server, and then start this job remotely. The SSIS license is only needed on machine where the package is run.

  
  
  
• SSIS Runtime - free redistributable?