How to Schedule an SSIS package using Windows Task Scheduler ?

Hi @minh tran ,

You cannot run a SSIS package (.dtsx) without installing the SQL Server integration Services. The minimum requirements are the SSIS client tools and the DTEXEC utility so you must install the Integration Services shared feature from the SQL Server install media.

In other word, you may need to use sql agent job in SQL Server to schedule an SSIS package without using Windows Task Scheduler.

Reference here: sql-server-agent-jobs-for-packages

If you only want to Schedule an SSIS package using Windows Task Scheduler, please refer to below thread.

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/07e59dcd-7547-47b2-bcdd-3e188eef619a/how-to-run-a-ssis-package-using-bat-file?forum=sqlintegrationservices

Regards，

Zoe Hui

If the answer is helpful, please click "Accept Answer" and upvote it.

Yes you can use Task Scheduler for that but I don't know why you would. SQL already has support for running SSIS jobs on a schedule. You don't need TS for this and that would just be adding an extra thing to configure.

As for copying output somewhere else you should do that within SSIS as well in my opinion. I'm not sure what you mean by output but I'm guessing you're producing some sort of files. In that case have SSIS copy the files elsewhere when done. This keeps everything together in one package.

If you absolutely need to do work outside SSIS then you can refer to the older article here. It talks about how to do it. At this point though if you have post-SSIS steps to do then you might need to wrap the SSIS call in a script. But I would try doing all this in SSIS first.