We are using SSIS with SQL Sever 2005 / VS 2008.
My colleague insists that we cannot use a scripting component inside the SSIS package because this will introduce executable code into the process then the CLR will have to be installed on the database server that is executing the job. Installing anything (if it doesn’t exist already) on production machines would be problematic.
My question is, does adding the scripting component to a SSIS package cause it to have to call the CLR whereas SSIS did not have this dependency before?
Please refer the following MSDN link.
Hardware and Software Requirements for Installing SQL Server 2005
As per the documentation,
SQL Server 2005installs.NET Framework 2.0on the machine (except for theExpressedition, which requires manual install). SSIS packages require SSIS runtime engine. If you have that SSIS component installed, you don’t need to install any other component to execute the packages even if they useScript TaskorScript Component.Following is the direct quote from MSDN and screenshot #1 highlights the section in the MSDN.
Quote from the MSDN:
Hope that helps.
Screenshot #1: