October 14, 2008 at 7:29 pm
Any input will greatly appreciated.
October 14, 2008 at 8:46 pm
Any scheduling product that can run DTEXEC can be used to schedule a SSIS package. By far, the easiest is SQL Server Agent which knows a lot about SSIS packages.
October 15, 2008 at 8:44 am
I'll second Happycat's endorsement of SQL Agent jobs. When you create a new job and a new step, choose "SQL Server Integration Services Package" as the type then fill in the required information for the specific package.
Greg
December 2, 2008 at 2:58 am
Just follow the steps.
http://www.codeproject.com/KB/aspnet/Schedule__Run__SSIS__DTS.aspx
March 27, 2009 at 1:26 pm
You can use DTEXEC or DTEXECUI command utility to run the package. These are preferable ways since if you schedule packages using SQL Agent it will slowdown database activities. You need to build project and you will find the compiled version's of your packages . then using DTEXEC utility from command line or you can prepare bunch of packages in single batch file with .bat extension and then schedule them using windows scheduler.
March 29, 2009 at 5:36 am
I am not sure where you get your information from but ...
- running a SSIS package from SQL Agent will not affect database operations other than the potential use of resources on the server that is running the packages. If you have any specific information on this issue, can you post it so others in this forum can be better informed
- building a project in BIDS does not create a binary form of a SSIS package. It simply creates the necessary files for use by the SSIS deployment utility
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply