While bcp'ing data into a large table with several text fields,
I inadvertently forgot to include the -T parameter, and thus
truncated most of those text fields to 32768 bytes. Unhappily,
the error was discovered by my customer, and not me.

Yes, my first reaction was that I should have been more careful.
But then I thought, why do I need to worry about this 32K limitation
in 2012, when database servers have scores if not hundreds of
gigabytes of RAM, and are connected to multi-terabyte arrays?

So I'm asking: what is Sybase's rationale for sticking with this
32K relic long after it should have been retired?

Michael Heaney