Sqlservr.exe high memory utilization

[Sparks48]

I am running several SQL 2000 SP3 servers in my network that are being used for bulk loads and full text searches. We have already determined that the front application is killing the CPU by dedicating 1 thread all of the time. What is confusing me is that after restarting the server I watch the memory utilization of sqlservr.exe pegging through the roof, many times before users connect and I may only be running 1 or 2 databases averaging about 10GB in size each. I am curious to know if there is a fix, configuration issue or the database design is fubar.

Also what is the advantage of having more than 1 instance of SQL on the same server.


Thanks!!

 

[collierd]

This might help
I asked a similar question some time back

See thread183-422356 Task manager shows memory issues
Outlook was a completely seperate problem (this statement will make sense if you look at the thread)

Also see thread183-438914 Creating a second instance of SQL Server
This gives a little bit of detail pertaining to the implications of a second instance

We do actually have a second instance on a server and I use this as it means I can have a completely mirrored test environment without buying an extra server (budgetting reasons)
I also have a backup server which mirrors live for disaster recovery
For what we do I haven't really noticed any problems with memory/speed

Damian.