Hi there

Has anybody experienced Timeout issues on updating NText fields in SQL
Server 2005?

Ive been using a procedure in an MS Access application, to read in the
contents of an Ntext
field used for notes into a local string variable.

Then further notes are added to this and then an update statement writes it
back to the NText
field.

Ive used an updateText procedure but this is also timing out.

The field has been in use and has been updated to before.

many thanks

Chris

Chris Asaipillai (chris.asaipil***@btinternet.com) writes:
If you are SQL 2005, you should consider migrating from ntext to
nvarchar(MAX) which fits just as much data, but works like any other
varchar, and does not have all the quirks of ntext.

The timeout is something that happens on the client side. If you just
have the patience, you can change the timeout on the Command object
(if memory serves). If you don't have the patience, you will need to
tune the procedure. Unfortunately, I cannot assist with that, since you
did not include any code or table definitions.

random select a row based a weight column.
Timeout expire
Optimize this query
How can I insert a new field between existing field?
store results over network