You're looking for answers, but all I've got are questions. This doesn't bode well, but lets give it a shot and see where we can get!
The "best" answer for you is something that only you can decide. Everyone has their own ideas about what makes sense, and there is a lot of additional "baggage" that comes with and problem like this that will significantly color the answer(s) you get.
I'm a hardcore believer in two basic principles that are somewhat in conflict here. First and foremost, manage the data as closely to where it is stored as possible which means that you automate everything as "low" as possible in the software stack (usually at the SQL Server itself). Second and only slightly less important is that n-tier applications (with a database server, an application server, and a presentation/web server) need to be completely n-tier, so figure out which server ought to do a job and don't compromise without a compelling reason.
Keeping those two thoughts in mind, describe your environment again. Is it two tier, n-tier, a hybrid of the two, or something different? All of these are valid choices and each of them leads to a different answer to your original question.
Putting this same line of thinking another way, where do you currently schedule application tasks? For things that happen daily, weekly, monthly, quarterly, yearly, etc as part of the BUSINESS side of your application, where do those events happen now? In the future, where do you envision these events happening?
In theory, theory and practice are identical. In practice, theory and practice are unrelated.