 | |
SSIS or SQL Agent?
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
SSIS or SQL Agent? -
07-09-2008
, 03:36 PM
#2
| |||
| |||
|
|
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: |
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.
#3
| |||
| |||
|
|
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: |
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.
#4
| |||
| |||
|
|
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: |
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.
#5
| |||
| |||
|
|
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: |
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.
#6
| |||
| |||
|
|
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: |
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.
#7
| |||
| |||
|
|
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: |
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.
#8
| |||
| |||
|
|
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: |
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.
#9
| |||
| |||
|
|
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: |
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.
#10
| |||
| |||
|
|
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. |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.