Post reply

Accidentally set max server memory to 0

  • November 26, 2015 at 9:20 am

    #1842529

    webrunner (11/24/2015)

    Thanks for this thread. I realize that being careful is the way to avoid this issue, but my question is, why is this change even possible in SQL Server? The max memory setting should never accept a value below the minimum SQL Server needs to start up, shouldn't it? I just don't see the point of allowing 0 to be set for max server memory.

    Just curious.

    Thanks,

    webrunner

    I'd have to chalk it all up to people still being human. You could also ask a thousand other questions about SQL Server like why do you get a tool tip when you click on an XML graph instead of something you can copy, etc, etc, ad infinitum.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing post 16 (of 15 total)

You must be logged in to reply to this topic. Login to reply