|
|
|
date: Wed, 9 Jul 2008 13:36:00 -0700,
group: microsoft.public.sqlserver.dts
back
Re: SSIS or SQL Agent?
Ditto on M's suggestion.
Each of the tools mentioned is good for its intended purpose. Yes, you could
create a continually running SSIS package that dynamically polls the system
date and time and does something in response, but the question is, "Why would
you want to?" And yes, you could create complex job steps inside of SQL Agent
that do all the complex tasks, etc. but again, why?
SSIS is good for your "complex logic".
SQL Agent is good for scheduling and controlling the job.
--
Todd C
"matteus" wrote:
> On Jul 9, 10:36 pm, mscertified wrote:
> > We need to set up a monthly 'job' that reads and writes from our SQL Server
> > 2005 database and creates FTP files. The logic is quite complex, its goes way
> > beyond a simple transfer of data. Would it be better to use SSIS or SQL
> > Server Agent to do this? What are the pros and cons? Thanks.
>
> > The logic is quite complex
> That is the point. SSIS is much more powerful than sqlserver agent:
> with ssis you can create a package: move, transform, edit and ftp your
> data. With sqlserver agent you can also create simple step that runs
> scripts or stproc, but imho is mainly for filesystem tasks or for
> scheduling an operation (such a package).
> I would definetly create a ssis package and then schedule it with
> agent.
>
> M.
>
date: Thu, 10 Jul 2008 05:45:01 -0700
author: Todd C
|
|
