Overallocation of Memory - SQL SERVER LOCKED UP

greenspun.com : LUSENET : SQL Server Database Administration : One Thread

I have accidentally allocated more memory in server config than I have physical memory. I can not start sequel server. I tried to start the device with the parameters -m and then -c . Both times I received a 2140 error. I can't believe microsoft does not have an easy fix for this. Any immediate help would be greatly appreciated. thanks

-- Anonymous, July 08, 1998


Re: Overallocation of Memory - SQL SERVER LOCKED UP


I think you need to use the -f option to start SQL Server in a minimal configuration.

This is useful if the setting of a configuration value (for example, over-committing memory) has prevented the server from starting. For more information, see Starting SQL Server with Minimal Configuration.

Under some conditions it may be necessary to stop the SQL Executive service (if it is running) in order to connect to SQL Server after it has been started with the -f option.

I hope this helps.


-- Anonymous, July 09, 1998

Moderation questions? read the FAQ