Tejesh,
I doubt very much if using UPDATETEXT (or even WRITETEXT) will cause a
memory leak in SQL Server (version ? ) when using Full-Text Search (FTS) to
the best of my knowledge. What you may be seeing is more memory usage by SQL
Server with the UPDATETEXT as only reads or scans the FT-enabled table's
rows.

If you're monitoring SQL Server memory usage via the Task Manager, then that
is the incorrect place to monitor SQL Server's memory usage instead you
should use Perfmon's Private Bytes counter under Perfmon's Process objects.
Specifically, "Private Bytes is the current size, in bytes, of memory that
this process has allocated that cannot be shared with other processes."

Regards,
John


[quoted text, click to view]

Can someone let me know if using UPDATETEXT can cause a memory leak in SQL
Server when using FULL Text Search ?

Thanks