In our data integration development team, I am proposing that we all use SQL Agent to schedule jobs, the majority of which will be compliled console apps that move data around. We can then use email notifications etc if something goes wrong with one
of the jobs.
Mainly SQL Server runs as a dedicated server to do it's work: Managing data.
You could use SQL Server Agent to schedule the execution of external applications, but the most avoid this to prevent a instability or resource leakness may caused by this external apps. And you also won't be able to scale out your application architecture,
because by this design everything is running on one server; it won't be any longer a dedicated SQL Server.
* cogito ergo sum * errare humanum est * quote erat demonstrandum *
Wenn ich denke, ist das ein Fehler und das beweise ich täglich Blog