FreeTDS Development Group

["Thompson, Bill D (London)" <bill_d_thompson AT ml.com>]

Thanks for this James,

I've always been slightly uneasy about text columns, although I know they
have worked in the past.

> Our BCP implementation doesn't do TEXT columns.  

Unlike you to be so imprecise :-)
If it were anyone else, I'd ask the following questions:

which version of freetds ?
which version of which database ?
freebcp or the dblibrary "sendrow" API ?
all text columns, or just very large ones ?

My version of freebcp works just fine.....

1> create table bill_bcp_text_test (col1 int not null, col2 text )
2>
1>

$ cat bill_bcp_text_test.txt
1       ABCDEFGHIJKL<
2       asdasdasdasda
3

$ freebcp MYDB..bill_bcp_text_test in bill_bcp_text_test.txt -c -S MYSERVER
-U MYUSER -P MYPASSWORD

Starting copy...

3 rows copied.

1> select * from bill_bcp_text_test
col1                col2
-------------------   -----------------------------------------------
                 1   ABCDEFGHIJKL<
                 2   asdasdasdasda
                 3   
(3 rows affected)
1>

My (production) version of freetds is, however, a "pre-iconv" snapshot of
0.62
So, I guess you're using something a little more up to date, and its gotten
broken.somewhere down the line...

I'll test my new code, and check out text columns specifically..


Bill


> -----Original Message-----
> From: Lowden, James K [SMTP:LowdenJK AT bernstein.com]
> Sent: 10 June 2004 21:57
> To:   TDS Development Group
> Subject:      [freetds] bcp text upload trace
> 
> Our BCP implementation doesn't do TEXT columns.  Neither does it complain;
> it just hangs because the server doesn't respond.  
> 
> For your enjoyment, attached is tcpdump output of an upload to a table
> having a single column, of type TEXT.  The tools used were:
> 
> $ bcp -v
> BCP - Bulk Copy Program for Microsoft SQL Server.
> Copyright (c) 1991-1998, Microsoft Corp. All Rights Reserved.
> Version: 7.00.623
> 
> $ isql -E -Smpquant -Q"select @@version"
>         --------------------------------
>  Microsoft SQL Server  2000 - 8.00.818 (Intel X86)
>         May 31 2003 16:08:15
>         Copyright (c) 1988-2003 Microsoft Corporation
>         Enterprise Edition on Windows
>          NT 5.0 (Build 2195: Service Pack 3)
> 
> and
> 
> $ windump -w textbcp.tcpdump -xX -s1500 tcp and host mpquant and port 2500
> and host ntc0272
> 
> I thought perhaps we could at least decode what's going on.  That would
> make it easier to add the functionality.  
> 
> Thank you for your kind attention.  
> 
> --jkl
> 
> 
>  <<textbcp.tcpdump.upload.text>> 
> 
> 
> -----------------------------------------
> The information contained in this transmission may contain privileged and
> confidential information and is intended only for the use of the person(s)
> named above. If you are not the intended recipient, or an employee or
> agent responsible for delivering this message to the intended recipient,
> any review, dissemination, distribution or duplication of this
> communication is strictly prohibited. If you are not the intended
> recipient, please contact the sender immediately by reply e-mail and
> destroy all copies of the original message. Please note that we do not
> accept account orders and/or instructions by e-mail, and therefore will
> not be responsible for carrying out such orders and/or instructions.
> If you, as the intended recipient of this message, the purpose of which is
> to inform and update our clients, prospects and consultants of
> developments relating to our services and products, would not like to
> receive further e-mail correspondence from the sender, please "reply" to
> the sender indicating your wishes.  In the U.S.: 1345 Avenue of the
> Americas, New York, NY 10105.
>  << File: textbcp.tcpdump.upload.text >>  << File: ATT2247823.txt >> 

==============================================================================

If you are not an intended recipient of this e-mail, please notify
the sender, delete it and do not read, act upon, print, disclose,
copy, retain or redistribute it.

Click here for important additional terms relating to this e-mail.
     <http://www.ml.com/email_terms/>

==============================================================================