SSIS or SQL Agent?

#11

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:

Quote:

On Jul 9, 10:36 pm, mscertified <rup... (AT) tigerlily (DOT) com> 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.

#12

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:

Quote:

On Jul 9, 10:36 pm, mscertified <rup... (AT) tigerlily (DOT) com> 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.

#13

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:

Quote:

On Jul 9, 10:36 pm, mscertified <rup... (AT) tigerlily (DOT) com> 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.

#14

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:

Quote:

On Jul 9, 10:36 pm, mscertified <rup... (AT) tigerlily (DOT) com> 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.

#15

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:

Quote:

On Jul 9, 10:36 pm, mscertified <rup... (AT) tigerlily (DOT) com> 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.

#16

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:

Quote:

On Jul 9, 10:36 pm, mscertified <rup... (AT) tigerlily (DOT) com> 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.

#17

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:

Quote:

On Jul 9, 10:36 pm, mscertified <rup... (AT) tigerlily (DOT) com> 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.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SSIS or SQL Agent?

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

Re: SSIS or SQL Agent? - 07-10-2008 , 07:45 AM

Re: SSIS or SQL Agent? - 07-10-2008 , 07:45 AM

Re: SSIS or SQL Agent? - 07-10-2008 , 07:45 AM

Re: SSIS or SQL Agent? - 07-10-2008 , 07:45 AM

Re: SSIS or SQL Agent? - 07-10-2008 , 07:45 AM

Re: SSIS or SQL Agent? - 07-10-2008 , 07:45 AM

Re: SSIS or SQL Agent? - 07-10-2008 , 07:45 AM