Also to point out and speaking from a bit of experience where I made a Phat Phinger mistake... BE VERY VERY CAREFUL WHEN MAKING THE SETTING CHANGE!!!! If you screw up and tell the server to only use, say, 100MB max memory by mistake, you may not be able to fix it and because you won't be able to start SQL Server to fix it.
yeah, I did this too. There is a way to force the memory setting on startup. It's a traceflag somewhere. If you do make this happen (as I did), you can get out of it... after a lot of panicked searching on the web.
-f startup switch, to start in minimal configuration
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass