Run SSIS packages within SQL Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hello,

When I designed and deployed DTS packages, I often stored them in SQL Server
or in the file system and ran them from batch scripts (using DTSRun.exe) or
from ASP.NET applications (either case, most of them weren't run at the SQL
Server itself).

I was hoping I could do the same with SSIS, but it seems you can't run SSIS
packages from servers without SSIS installed, and SSIS requires a SQL Server
license... Since I'm stuck with a single SQL Server, the implications of
this is that I have to run the SSIS packages from my SQL Server.

I'm not happy about the prospect of running batch scripts and ASP.NET
applications on the SQL Server, so I was hoping there is some way I can
execute the packages using T-SQL or something similar? I need to start the
SSIS packages from batch scripts and ASP.NET applications, and I also need
to set variables in the packages before I run them...

Any suggestions? I'm interested in hearing any best practices here!
Performance-wise, I don't mind that the SQL Server needs to run the packages
itself, and I'm sure in the end, I'll find a robust and flexible way of
running the packages from within SQL Server... I just need some help getting
there :-)

Thanks!


Regards,
Nils Magnus


.

Relevant Pages

  • Re: no dtsrun.exe on sql for 64b servers??
    ... instructions on Selecting 32-bit or 64-bit Package Execution. ... If you point to the right path for the DTSRUN executable, just as SSIS can ... Services packages that were created in earlier versions of SQL ... SQL Server 2005 Integration Services Backward Compatibility ...
    (microsoft.public.sqlserver.dts)
  • Re: SQL 2005: How do I access saved SSIS packages
    ... When I go through the Import/Export Wizard and select the option to save the ... In EM in SQL Server 2000, I could see the saved DTS packages by going to ... Transformation Services>Local Packages. ... locally saved SSIS packages. ...
    (microsoft.public.sqlserver.dts)
  • RE: DTS 2000 package error when connecting to SQL Server 2005
    ... For the purpose of getting to SQL Server 'Objects', ... SSIS is not really that big of a beast. ... In the Solution Explorer on the right, right click on the SSIS Packages node ... Todd Chittenden ...
    (microsoft.public.sqlserver.dts)
  • Re: Upgrading DTS to SSIS
    ... You cannot run packages outside of BI Development Studio on a client computer that does not have Integration Services installed, and the terms of your SQL Server 2005 licensing may not permit you to install Integration Services on additional computers. ... SQL Server 2005 Integration Services (SSIS) is now a server component and is not redistributable to client computers in the same manner that the components required for SQL Server 2000 Data Transformation Services (DTS) were redistributable. ...
    (microsoft.public.sqlserver.dts)
  • Re: Editing DTS Packages on a 64-bit SQL Server 2005 installation
    ... The tips for running 32-SSIS packages can be extended to running 32-bit DTS ... store your DTS packages in a 64-bit SQL Server database. ... have tried installing the Web download it says to install but then I get ...
    (microsoft.public.sqlserver.setup)