SQL memory issues and Reason 0
We're having a bit of a nightmare with sims.net and the March update. Although I'm not convinced the march update has anything to do with it as our problems starting happening about 3 weeks ago.
Basically we're getting the Reason 0 when people try to login. At first it was random people, which turned into the whole school. After speaking to capita, they suggested that we do admin work directly on the server as this with use SQL named pipes and should there be a problem, it will not lock the whole database in maintenance mode.
We tried this and it seemed to work for a little bit.
Roll forward to today. I performed the March 2009 update last night and all worked ok. I logged into a number of machines and the update run fine. We already had some users who still were getting the Reason 0 problem before the update. They still had the problem after the update, along with some new staff. Capita suggested resetting their passwords in system manager. This actually worked. However, those same people are now getting the same problem. Only this time when we try and reset their password, it doesn't seem to make any difference. Still Reason 0.
Our sims.net server is running under Virtual Server 2005r2 but here is the spec.
Hosting Server: Dell PowerEdge 2950, 2 x Quad Xeon E5320, 16GB Ram, 1TB SAN
Virtual Server (for sims.net): Windows 2003r2, 3.7GB Ram
One thing I have notice is that SQL doesn't use any more then 1.7GB. Yet I've assigned 3.7GB to the server. Is there a way I can allocate another 1GB of ram to SQL with it making the machine too slow. Surely that's got to help?
Still waiting for capita to get back about the reason 0 issues. I know the detaching the database and reattaching will fix it but it's not ideal. Finance are doing their year end at the moment so they won't be too happy.
any help greatly received.