December 7, 2004 at 8:03 am
I have the following code:
declare @ptrval binary(16)
select
@ptrval = TEXTPTR(Sat_Narrative)
from
ex_DataTable
where
AgencyID = '27-02'
and ReportMonth = 11.0
updatetext ex_DataTable.Sat_Narrative @ptrval 0 0 'This is sample text xxxxxxxxxxxxx xxxxxxxxx xxxxxxxxxxxxxxx xxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxx xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.'
READTEXT ex_DataTable.Sat_Narrative.Sat_Narrative @ptrval 0 0
But when this is run it is truncating everything after the first 50 characters. The Sat_Narrative column is defined as a nText.
Any ideas would be greatly appreciated
Arthur Lorenzini
December 7, 2004 at 8:10 am
See, if this helps:
http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/part3/c1161.mspx
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
December 7, 2004 at 9:53 am
I am not sure what the problem is even after reading the article. The contents of the ntext is only 724 bytes.
Arthur Lorenzini
December 7, 2004 at 12:40 pm
This is a shot in the dark because I don't have time to remember how all that works, but...
Since your datatype is NTEXT shouldn't your statement use the "N" prefix before the literal string?
updatetext ex_DataTable.Sat_Narrative @ptrval 0 0 N'This is sample text xxxxxxxxxxxxx xxxxxxxxx xxxxxxxxxxxxxxx xxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxx xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.'
This may not be it at all, but that's what leaps out at me at a glance.
December 7, 2004 at 1:36 pm
i wrote a quick and dirty VB6 program to make sure the data was being stored completely in the ntext column which it was. I discovered that the solution was a setting on the Query Analyzer under the Tools\Option and the Result Tab and increased the Maximum character per column setting. Thanks for all your input.
Arthur Lorenzini
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply