While I can't speak for Simon's experience, we are running with 16 Gigs on a
x64 bit machine (DL 585) and its running fine. We have set our max memory to
"CR" <me@work.com> wrote in message
news:%23KPQntwOHHA.1248@TK2MSFTNGP03.phx.gbl...
> Ok, that brings up another question, our server is set to boost SQL Server
> priority, would this slow down msftesql? We are running 4 3.2 Xeon's with
> 8 GB RAM (Maxmem is set to 7168 MB). We have 14 fulltext indexes with
> approximately a million rows each, but within the next month we will be
> adding 12 more fulltext indexes which, I believe, will be slightly larger,
> and doubling our db size (currently we have 63 tables, the largest being
> 10 million rows, and total used mdf size is 17 GB). Do you think the boost
> SQL Server setting will be slowing fulltext indexing? Or does this setting
> also boost the priority of msftesql? Do you think the max memory setting
> above is giving msftesql the room it needs?
> Thanks.
> CR
>
> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
> news:eBdoVYwOHHA.4372@TK2MSFTNGP04.phx.gbl...
>> This is normal, you might want to limit max memory size to something
>> smaller to give room for MSFTESQL.
>>
>> --
>> Hilary Cotter
>>
>> Looking for a SQL Server replication book?
>>
http://www.nwsu.com/0974973602.html >>
>> Looking for a FAQ on Indexing Services/SQL FTS
>>
http://www.indexserverfaq.com >>
>>
>>
>> "CR" <me@work.com> wrote in message
>> news:ua5ZcFwOHHA.5064@TK2MSFTNGP04.phx.gbl...
>>> Our performance is currently fine, but we are planning on adding more
>>> full
>>> text indexes, so I have question.
>>> Our database server is experiencing between 2,000 and 10,000 page faults
>>> per second on msftesql.exe, as shown in task manager on the processes
>>> tab, is this normal for a relatively busy website (50
>>> million hits daily) with full text?
>>>
>>>
>>>
>>
>>
>
>