![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
On Jun 19, 12:35 am, Frank Xia <Frank... (AT) discussions (DOT) microsoft.com wrote: I need to schedule a SQL Script to process and then EXPORT to .CSV file.....and then....either EMAIL out the file...OR.... FTP it to a clients site....? Can I get some guidance on the best approach to accomplishing this..?? Thanks a lot! Hi frank, I would build a dts package, and - create a connection for your source (i suppose you use sqlserver 2000 then an oledb connection should be the best) - create a connection for the target (the excel file) - use the Trasform Data task and link the two connections. then if your clients are inside your lan i would rather create the file directly on the clients. Email could be better but, for SQL2000 i think (not completely sure) that you must have outlook installed on your dbserver on which the sqlserver services (agent) run in order to use the Send Mail task. Alternatively you could use some free command line mailing programs (try blat.exe) but your mailserver must allow relaying... Once you have built the package you can schedule it in a job with SqlServer agent. Bye, M. |
#12
| |||
| |||
|
|
On Jun 19, 12:35 am, Frank Xia <Frank... (AT) discussions (DOT) microsoft.com wrote: I need to schedule a SQL Script to process and then EXPORT to .CSV file.....and then....either EMAIL out the file...OR.... FTP it to a clients site....? Can I get some guidance on the best approach to accomplishing this..?? Thanks a lot! Hi frank, I would build a dts package, and - create a connection for your source (i suppose you use sqlserver 2000 then an oledb connection should be the best) - create a connection for the target (the excel file) - use the Trasform Data task and link the two connections. then if your clients are inside your lan i would rather create the file directly on the clients. Email could be better but, for SQL2000 i think (not completely sure) that you must have outlook installed on your dbserver on which the sqlserver services (agent) run in order to use the Send Mail task. Alternatively you could use some free command line mailing programs (try blat.exe) but your mailserver must allow relaying... Once you have built the package you can schedule it in a job with SqlServer agent. Bye, M. |
#13
| |||
| |||
|
|
On Jun 19, 12:35 am, Frank Xia <Frank... (AT) discussions (DOT) microsoft.com wrote: I need to schedule a SQL Script to process and then EXPORT to .CSV file.....and then....either EMAIL out the file...OR.... FTP it to a clients site....? Can I get some guidance on the best approach to accomplishing this..?? Thanks a lot! Hi frank, I would build a dts package, and - create a connection for your source (i suppose you use sqlserver 2000 then an oledb connection should be the best) - create a connection for the target (the excel file) - use the Trasform Data task and link the two connections. then if your clients are inside your lan i would rather create the file directly on the clients. Email could be better but, for SQL2000 i think (not completely sure) that you must have outlook installed on your dbserver on which the sqlserver services (agent) run in order to use the Send Mail task. Alternatively you could use some free command line mailing programs (try blat.exe) but your mailserver must allow relaying... Once you have built the package you can schedule it in a job with SqlServer agent. Bye, M. |
#14
| |||
| |||
|
|
On Jun 19, 12:35 am, Frank Xia <Frank... (AT) discussions (DOT) microsoft.com wrote: I need to schedule a SQL Script to process and then EXPORT to .CSV file.....and then....either EMAIL out the file...OR.... FTP it to a clients site....? Can I get some guidance on the best approach to accomplishing this..?? Thanks a lot! Hi frank, I would build a dts package, and - create a connection for your source (i suppose you use sqlserver 2000 then an oledb connection should be the best) - create a connection for the target (the excel file) - use the Trasform Data task and link the two connections. then if your clients are inside your lan i would rather create the file directly on the clients. Email could be better but, for SQL2000 i think (not completely sure) that you must have outlook installed on your dbserver on which the sqlserver services (agent) run in order to use the Send Mail task. Alternatively you could use some free command line mailing programs (try blat.exe) but your mailserver must allow relaying... Once you have built the package you can schedule it in a job with SqlServer agent. Bye, M. |
#15
| |||
| |||
|
|
On Jun 19, 12:35 am, Frank Xia <Frank... (AT) discussions (DOT) microsoft.com wrote: I need to schedule a SQL Script to process and then EXPORT to .CSV file.....and then....either EMAIL out the file...OR.... FTP it to a clients site....? Can I get some guidance on the best approach to accomplishing this..?? Thanks a lot! Hi frank, I would build a dts package, and - create a connection for your source (i suppose you use sqlserver 2000 then an oledb connection should be the best) - create a connection for the target (the excel file) - use the Trasform Data task and link the two connections. then if your clients are inside your lan i would rather create the file directly on the clients. Email could be better but, for SQL2000 i think (not completely sure) that you must have outlook installed on your dbserver on which the sqlserver services (agent) run in order to use the Send Mail task. Alternatively you could use some free command line mailing programs (try blat.exe) but your mailserver must allow relaying... Once you have built the package you can schedule it in a job with SqlServer agent. Bye, M. |
#16
| |||
| |||
|
|
On Jun 19, 12:35 am, Frank Xia <Frank... (AT) discussions (DOT) microsoft.com wrote: I need to schedule a SQL Script to process and then EXPORT to .CSV file.....and then....either EMAIL out the file...OR.... FTP it to a clients site....? Can I get some guidance on the best approach to accomplishing this..?? Thanks a lot! Hi frank, I would build a dts package, and - create a connection for your source (i suppose you use sqlserver 2000 then an oledb connection should be the best) - create a connection for the target (the excel file) - use the Trasform Data task and link the two connections. then if your clients are inside your lan i would rather create the file directly on the clients. Email could be better but, for SQL2000 i think (not completely sure) that you must have outlook installed on your dbserver on which the sqlserver services (agent) run in order to use the Send Mail task. Alternatively you could use some free command line mailing programs (try blat.exe) but your mailserver must allow relaying... Once you have built the package you can schedule it in a job with SqlServer agent. Bye, M. |
#17
| |||
| |||
|
|
On Jun 19, 12:35 am, Frank Xia <Frank... (AT) discussions (DOT) microsoft.com wrote: I need to schedule a SQL Script to process and then EXPORT to .CSV file.....and then....either EMAIL out the file...OR.... FTP it to a clients site....? Can I get some guidance on the best approach to accomplishing this..?? Thanks a lot! Hi frank, I would build a dts package, and - create a connection for your source (i suppose you use sqlserver 2000 then an oledb connection should be the best) - create a connection for the target (the excel file) - use the Trasform Data task and link the two connections. then if your clients are inside your lan i would rather create the file directly on the clients. Email could be better but, for SQL2000 i think (not completely sure) that you must have outlook installed on your dbserver on which the sqlserver services (agent) run in order to use the Send Mail task. Alternatively you could use some free command line mailing programs (try blat.exe) but your mailserver must allow relaying... Once you have built the package you can schedule it in a job with SqlServer agent. Bye, M. |
![]() |
| Thread Tools | |
| Display Modes | |
| |