Wow.  You are using SQL Server?  This is a varchar column?

It's hard to believe that SQL Server just up and suddenly decided to start
truncating a column.

I assumed you've checked the table definition to insure that the column is
still defined properly.
You should next check the updating (ASP?) code to ensure that it's not doing
anything untoward.  Where does this 6000 character string come from?  If the
source of this data was inserting ASCII 0 into the middle of the string, the
string will look like it got truncated in things like query analyzer and EM,
and client tools will choke on it as well.

Are there any other variable character columns which suddenly started
getting large?  There is a limit  of 8060 characters to a row, and I suppose
if the code doing the update wasn't properly handling the error that would
occur when a too large update was done that you could see this behavior,
although I admit I'm grasping at straws here...

--
Jeff Mason			Custom Apps, Inc.
Jeff@c...

-----Original Message-----
From: henryh@p... [mailto:henryh@p...]
Sent: Tuesday, August 13, 2002 7:00 PM
To: sql language
Subject: [sql_language] RE: Insert Into Statement


Tried that and exporting the data to a file and both ARE being cut