April 26, 2017 at 10:48 am
spitfire677 - Wednesday, April 26, 2017 10:40 AMLynn Pettis - Wednesday, April 26, 2017 10:19 AMspitfire677 - Wednesday, April 26, 2017 10:16 AMLynn I was running CFMX7 on the old server. The new one is a VPS running CF10. I will start looking at CF to see if it could be the source of the problem.Check the configuration of Cold Fusion. Make sure it isn't defaulting to Unicode data types. The older version was all or nothing (this caused us headaches when they started supporting Unicode data and set this configuration option).
I don't know how to check this. Looked in CF Admin, and looked at settings for the datasource... nothing there.
Can't help you there, I just do database stuff here. All the Cold Fusion work is done by our engineers. Check the Cold Fusion documentation is all I can offer.
April 26, 2017 at 10:48 am
spitfire677 - Wednesday, April 26, 2017 10:40 AMLynn Pettis - Wednesday, April 26, 2017 10:19 AMspitfire677 - Wednesday, April 26, 2017 10:16 AMLynn I was running CFMX7 on the old server. The new one is a VPS running CF10. I will start looking at CF to see if it could be the source of the problem.Check the configuration of Cold Fusion. Make sure it isn't defaulting to Unicode data types. The older version was all or nothing (this caused us headaches when they started supporting Unicode data and set this configuration option).
I don't know how to check this. Looked in CF Admin, and looked at settings for the datasource... nothing there.
Does this link help:
http://www.asadesigner.com/13-coldfusion/ef082eaf4dcb02c9.htm
the response/answer was:
In the Cold Fusion Administrator, ODBC Datasources, there are two options relevant to text retrieval:
a checkbox labeled "Long Text Retrieval Settings " with the description "Enable retrieval of long text -
Enable this option only if you want to retrieve all the data for a long text field. If the option is not selected ColdFusion retrieves the number of characters specified in the long text buffer size. Enabling this option may compromise performance. "
below that is an input box labeled "Long Text Buffer Size " which defaults to 6500 characters
Try checking the first box, or increasing the value in the second input box.
If that doesn't work, count the number of characters returned, to determine if it always "clips" it at the same position. Another thing that happens, which is plaguing me right now, is in a record edit form if you set a variable's value to a query column result that contains double quotes, and use that variable in a form input, the displayed value gets truncated when output. That is because Cold Fusion escapes form or query output, but not if you CFSET that output to a variable.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
April 26, 2017 at 11:00 am
Lynn I found some interesting setting in CF Admin under Datasources - Advanced settings. They are:
"Enable Long text retrieval - CLOB" , not currently checked
"Enable Binary Large Object Retrieval - BLOB" , not currently checked
"Long Text Buffer (chr)" - Currently set to 64000
"BLOB buffer (bytes)" - currently set to 64000
I will research these settings after lunch aliong with the link bmg002 sent Thanks bmg! I think we are on to something here!
April 26, 2017 at 12:00 pm
Thanks to all!! Although it turned out to not be a problem with MS SQL Server or coding the discussion here led me to the right answer.
I work at home by myself so it is great to have some outside input!
Checking the "Enable Long text retrieval - CLOB" box solved the problem. I also increased the buffer size but that was probably not needed and wi;; experiment with changing back.
All the best guys!
Mike
April 26, 2017 at 12:37 pm
You are welcome.
Plus, you don't know how often the database is blamed for problems that aren't the fault of the database.
In the end, we all have to work together.
April 26, 2017 at 12:50 pm
Lynn Pettis - Wednesday, April 26, 2017 12:37 PMYou are welcome.
Plus, you don't know how often the database is blamed for problems that aren't the fault of the database.
In the end, we all have to work together.
Exactly. And since DBA stands for Default Blame Acceptor, I know I often just suck it up and then try to prove it wasn't the database and attempt to provide a good second place to look.
It sometimes is the database, but it is always good to check out the non-database things too.
Glad you got it sorted out.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply