I have a Compaq web server that is currently running IIS5 (obviously) with SQL Server. I know that running SQL Server on the same machine as a web server is not ideal, but the site is still fairly small and the budget doesn't extend to 2 servers yet.
Anyway when I restart the box everything runs fine. Then SQL Server starts to build up its memory usage (it's configured to take as much memory as it needs up to 80% of total RAM). When the memory usage is fairly high (475Mb out of 527Mb of actual memory - it shouldn't be using virtual memory) my searches start to crawl. If I observe the process manager when t's searching, I notice that lsass.exe and not sql server is taking up the most CPU time though. Why might this be? SQL Server doesn't even use Windows login - I've configured it to use it's own login. I'm at a complete loss.
Anyway when I restart the box everything runs fine. Then SQL Server starts to build up its memory usage (it's configured to take as much memory as it needs up to 80% of total RAM). When the memory usage is fairly high (475Mb out of 527Mb of actual memory - it shouldn't be using virtual memory) my searches start to crawl. If I observe the process manager when t's searching, I notice that lsass.exe and not sql server is taking up the most CPU time though. Why might this be? SQL Server doesn't even use Windows login - I've configured it to use it's own login. I'm at a complete loss.
