Push FTP
-
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/sjones/pushftp.asp
-
Pretty interesting. I agree that it doesn't make a lot of sense that the DTS task only does one way transfers - I've looked at the API recently and there ain't a lot of difference between get and put.
I like COM and compiled code for solutions, but for this I doubt it make much difference, would be style and not substance!
Andy
-
Personally I hate installing new software on my servers. I built this solution so that I could quickly and easily move this solution to another server without worrying about registering components, rebooting, etc.
In fact, I setup a new version of this DTS package on a server last week in about 3 minutes with no reboots.
Steve Jones
-
I agree about reboots - not an issue when you build your own...or as much of an issue anyway. I get a lot of use/reuse out of code in COM dll's.
Andy
-
You've wrapped it up nicely in ActX and no doubt it works great for you, but what about decent error information? I've been down this route but have converted to a COM DLL, so I can get meaningfull error messages. This was a no cost solution as I wrote the DLL and two seconds to install- copy file, register file.
Darren Green
Darren Green
SQLDTS.com | SQLIS.com | Konesans Ltd -
Kowabunga, someone who likes to compile code!
Andy
-
I'll admit the error handling is low here. I could add some in ActiveX easily, though http://ftp.exe isn't great for doing this.
I really wanted this solution because I can deploy it completely from sql without being at the server.
Steve Jones
-
Cool. I have a remote site that is about to rehost to W2K & S2K. Your solution will come in handy!
-
Glad it will help. I've got some more details for how I handle the other side of the backups I will post soon.
Steve Jones
-
Nice article steve. I had the same problem a while ago, I did basically the same thing with a command file for the command line ftp with a cmdshell to run it, works ok but not very clean. in the end, I got a programmer to whip up a com routine for ftp, the beauty of this is that I can specify a specific port which the command line http://FTP.exe does not allow, therefore, making it very restrictive under some circumstances.
Chris Kempster
www.chriskempster.com
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA" -
I've thought about using a COM component and am not opposed. The thing I really like about this method is I can copy a single file (.DTS) to a SQL Server and have it run as a task without any installations, registrations, reboots, etc. I can update this thing without affecting the server, and it works on every SQL Server.
Kind of a KISS solution.
thanks for the complement.
Steve Jones
-
I want to ftp my snapshot which is generated by SQL Server 2000's Replication function,but my configuration doesn't work.
can I ply for DTS?
-
I'd post some more information under the DTS forum and we'll try to help. Or under the replication section.
Steve Jones
-
I implemented a SQL Server Agent job to do these FTP Push tasks from NJ to CA without DTS. I found that the FTP Put will max out the T-1 between these locations.
Have you seen this?
Andy
-
The thing that always irked me thou with the built in FTP component is how poorly it performs. I deal with very larg files sometimes and with http://ftp.exe and set as binary transfer type versus the ftp component will have drastic differences in speed. I have tested a couple of components and have yet to see anyone reach the same speed but the majority do outperform the built in component. So I choose to use the command line interface and avoid the cost when I only have about half dozen transfers and their all static in nature.
Viewing 15 posts - 1 through 15 (of 20 total)
You must be logged in to reply to this topic. Login to reply