Changing Configuration Values When SQL Server Won't Start
----- Original Message -----
From: David V. Brenner <firstname.lastname@example.org>
> 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: