SQL Agent Job vs Quartz.net

[Jerry Wang]

I need to write a schedule job application to manage our company's
data importing/exporting process ( stand alone application )
I want to use Quartz .net, my supervisor who is a DBA suggested using
SQL Server Agent job.

Here is what I need the scheduler to do ,

1. schedule the same EXE application but passing different
parameters.

2. can be accessed through a web-based GUI ( I can develop one ) to
manage the schedule, see the logs and status.

it looks like both SQL job and Quartz can do this, but I have never
heard of anyone suggesting using SQL Job.

Is there any significant disadvantage of SQl Server Agent Job
scheduler ?

[Scott White]

It depends really, if you just need to execute a SQL statement or an
SSIS package then a SQL Job would be adequate.

However if you write your own ETL in .Net and wanted to schedule this
then Quartz would be a better fit.

I don't like SSIS so I wrote my own ETL "engine" and used Quartz to
schedule different jobs within the ETL engine that ran as a service.

Regards,
Scott

Sent from my iPhone

> --
> You received this message because you are subscribed to the Google Groups "Quartz.NET" group.
> To post to this group, send email to quar...@googlegroups.com.
> To unsubscribe from this group, send email to quartznet+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/quartznet?hl=en.
>