Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Update times out when saving to a txt col with >1604 chrs

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2006-04-12 : 09:14:18
Tom writes "Environment: SQL2000/SP3 (Std Ed) running on Windows 2000; simple VB6 data entry application with all record transactions performed via stored procedures.

We have been using a VB6 front-end application (developed inhouse) to a SQL2000 server for a long time with out any issues. Today, our admin assistant reported that when she tried to save a record it was timing out. After digging into the code, it became clear that the issue was related to a "comments" text field on the entry form (used for entering l-o-n-g narratives) that is stored in a text data-type column in the SQL database. After running several tests, I determined:

1) If the "comments" text column for a record was INITIALLY BLANK in the database and I then entered less than ~1604 characters into the "comments" field on the entry form and updated the record, the update completed successfully. If I entered more than ~1604 characters into the "comments" field, the update would timeout. Again, in both circumstances the text column was initially blank.

2) If, however, I first entered even a single character into the "comments" field and updated the record (successful), and then enter another 2000+ characters into the field and updated the record again, guess what, success!!??

It appears that the initial state of the text column (empty vs. containing even a single character) is creating this wierd behavior.

3) And since I don't believe in coincidences, another VB6 application began failing yesterday. The program is used to store digital images (into an image/BLOB datatype column). If a user tries to import a record containing an image and associated metadata into the database the transaction times out. This problem also happened several months ago, but the issue mysteriously fixed itself in a few days before I was able to determine a cause.

Given that text and image datatype columns actually contain pointers to the real data stored elsewhere, I was wondering if the issues described above are related. Any help in solving these issues would be much appreciated. I have no idea where to begin troubleshooting.

Thanks,

Tom"
   

- Advertisement -