msftesql memory usage

We have been testing SQL 2005 full-text search, and noticed that the
msftesql process isn't using much memory (only around 6 megs), when the
single table we're indexing has about 3.8 millions rows, with 4 varchar
columns indexed ranging between varchar(255) and varchar(750). Is this
normal, i.e., is the full text search service using sqlservr.exe's memory?
Our server is a 2-way 2.0 GHZ opteron with 4GB RAM using WIN2K server with
/3GB switch.
We've looked around for a way to increase the memory available to msfteql
without success.
Thanks,
John
John,
Yes, its normal, but you can control the "aggressiveness" of the SQL Server
2005 MSFTESQL service via several advance sp_configure settings. Run the
below SQL code and review the new fulltext search options:
use master
go
sp_configure 'show advanced options', 1
reconfigure with override
go
sp_configure
There should be several new option to allow you to control the memory
allocation of the MSFTESQL service. No, the MSFTESQL uses its own memory
separate from the SQL Server memory.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"John" <jglass67@.msn.com> wrote in message
news:uocvvK2lFHA.764@.TK2MSFTNGP14.phx.gbl...
> We have been testing SQL 2005 full-text search, and noticed that the
> msftesql process isn't using much memory (only around 6 megs), when the
> single table we're indexing has about 3.8 millions rows, with 4 varchar
> columns indexed ranging between varchar(255) and varchar(750). Is this
> normal, i.e., is the full text search service using sqlservr.exe's memory?
> Our server is a 2-way 2.0 GHZ opteron with 4GB RAM using WIN2K server with
> /3GB switch.
> We've looked around for a way to increase the memory available to msfteql
> without success.
> Thanks,
> John
>

MSFTESQL blocking itself

I am populating a catalog (which is taking longer than on 2000) and when I look at the processes what is see is strange... MSFTESQL has many spids and each spid appears to have 4 connections. Of each set of 4 3 are blocked by 1... This seems odd to me. Also the CPU is at 90%-100% but it is not the MSFTESQL service. It is the SQL server hogging it all.

I have looked but can't find anything. I found information on it MSFTESQL is talking all the CPU but that won't help me. SQL 2005 is the only thing on this server (win 2003)... It only had 3.5 gb of ram but it is just testing ground for our app...

Any guidence in what to look at or alter would be great...

Look like the current syntax "alter fulltext index" does not allow indexed hint, maxdop. This would be a good request to file.

http://connect.microsoft.com/sql|||

Added a request as a bug.

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=260917