I started to do that. The table has 660K rows of data. After about 10 or 15 minutes, I finally canceled the query. I don't deem the number of rows to be extensive but when it's searching through an 8000 ntext field maybe the run-time isn't that extreme?? And, of course, I cannot put an index on the field in question due to the data type. Maybe I'll offload that table to a development server and just let the update run however long it takes and go from there. Thanks for the reply.