SQL-ftpd ftp server for SQL Server data retreival
Caveats
Warning: This document may be obsolete.
I can't think of any! Well, that's not true. Here's a few things I know of
so far:
- User defined data types aren't supported. You'll need to perform your own convert statement
so that the data is returned to you.
- The query length is limited by the ftp client. Some clients require the entire get command
be 72 characters or less, which makes the query very short. I can't change the clients, so
if your client has short command limitations, you might try putting the query in a stored
procedure and doing a get on the stored procedure. See Hints
for more information.
- Some clients have problems with the dir and ls commands. If your client maps
ls to dir, check for an nlist command. If not, see Hints
for a workaround.
- I've considered cancelling the timeout value, when a query is in progress. This however,
could be dangerous for some "runaway" queries, so I'm going to watch how it's used first.
- You must have a user id on the SQL server. If not, you'll get an access denied message.
- The port numbers should be stable, but they can't be made symbolic. Sorry.
- GUI clients are completely useless for this sort of server. Sorry.
- The SQL statement must be enclosed in quotes and a remote file name should always be specified.
- Novell's FTP client is dorked!!! I've hacked the server to try to work with it, but it should
be avoided if at all possible. This means that transfers to PC's may not work (but should).
Primarily, a cd command may fail, but you won't know it, because of Novell's FTP client
playing games with the RETR command. See Hints for more information.
Foward to the Revision History Page
Return to the SQL-ftpd Contents