FreeTDS Development Group

["James K. Lowden" <jklowden AT speakeasy.org>]

"Huckle, Steve" wrote:

> Hi,
>
> Yeah, I can get reads running, but not writes (using BCP)....they core dump.
>

Oh.  BCP did you say?  Oh my.

One of my roundtuit projects is to make BCP way better.  With all due respect 
(I mean
that) to the author, it's incomplete and not particularly obvious about it, 
until you
look at the source code.  Many functions simply return "success" without doing
anything.

Many features are missing.  Transactions and writes from memory (not a file) 
are two
that come to mind immediately.

Also, SQL Server 7.0 introduced many subtle changes (witness discussions here 
about
endians and  dates, null bits, wide varchars) to the TDS, and it's likely 
that some
of the fixes were "alongside" the BCP code.

If you're doing single-transaction uploads from a file to a table containing
long-established (pre 7.0) datatypes -- and you've applied SP3 to your server 
to
address date endian problems (because yours is a Solaris client, doesn't that 
mean
Sparc, big-endian?) -- then BCP uploads will probably work.  Outside those
parameters, I'd bet against it.

Glad to hear someone else *cares* about BCP.  Might raise my motivation, 
although the
weather is getting better, too.

HTH.

--jkl