Re: [Emerald] More fun than I'm allowed to have

Josh Hillman ( (no email) )
Sun, 15 Aug 1999 19:53:59 -0400

You probably didn't have 264144 kB available in RAM when you tried
restarting SQL. SQL won't start unless the specified amount of RAM is
available (this has nothing to do with the swap file).
Also, keep in mind that the memory setting that you changed is in 2k
increments--not 1, so if you entered in 262144, you told SQL to allocate
over 500MB of RAM to it when it starts. That RAM wasn't available, so SQL
didn't start.

Changing Configuration Values When SQL Server Won't Start


----- Original Message -----
From: David V. Brenner <>
> Just added 128 megs of RAM to my SQL box, for a total of 384.
> Tried to double the memory setting from 131072 (128 megs) to 262144 (256
> megs) in SQL Enterprise Manager. Also bumped the tempdb value from 32
> (megs) to 40 (megs). The "MSSQLServer" service wouldn't start. After
> panicking, I found that I had to run sqlservr -c -f and kill the
> SQLExecutive to even be able to run iSQL_W, at which point I was able to
> "sp_configure memory, 131072" and "sp_configure tempdb, 32" to get things
> running again.
> Which brings me to this...
> Any idea why 262144 would be a problem for the memory setting? It should
> take a much larger number than even that, as far as I know. If there was
> something wrong with the RAM physically, I would think it would have
> manifested itself in a somewhat different problem (i.e., blue screen) than
> simply preventing SQL (6.5) from starting up.

For more information about this list (including removal) go to: