Explicitly update a table after sp_tableoption "text in row" advices wanted I have an extremely slow sql server 2000 DB with 8GB, and the cause of this is the 3 ntext columns which are in the more queried table. Table has indexes set and also the full-text ssearch index set for these ntext columns, though when "select ntextcol1, ntextcol2 from table" the query takes up to 5min...crazy! But ofc when one knows which row to fecth, by its id which is indexed its fast!

To try to overcome this, I was trying to use sp_tableoption "text in row", 4000 but according to some Msft Technet reading, this will only be performed on existing records only when they're updated. So I was thinking in force an update in the rows so it would trigger the usage of the new option and hopefully have better performance.

This table as 100000 rows and seems scary stuff to do, so I was looking for some input from you and know if you have done it before, if it's a smooth process if any special advice...
Sounds to me you're missing indexes for the queries your application actually uses. select ntextcol1, ntextcol2 from table takes 5 min is not the point: this is a table scan that retrieves all LOBs. Your application (hopefully...) never issues this query. Pulling ntext (you should be using `NVARCHAR(MAX) btw) in row or pushing them out of row is not what you should be looking at.

Read General Index Design Guidelines and all the related articles in the section (clustered index design guidelines, non-clustered index guidelines etc etc). And learn how to identify the problem queries in your app, the indexes should target those queries: Troubleshooting Performance Problems in SQL Server 2005, Waits and Queues