• GilaMonster (4/26/2016)


    Grant Fritchey (4/26/2016)


    GilaMonster (4/26/2016)


    Grant Fritchey (4/26/2016)


    I do not recommend this because it will seriously negatively impact your startup time, but if you really want it to immediately use the memory you allocate for it, you can set the minimum to the higher value. Again, this is not recommended, but it is how you would do it..

    Sorry, but that's not what will happen.

    Minimum isn't what's allocated at startup. It's the value that, once allocated, SQL will not drop memory usage below. It'll still ramp memory up the same way it does with a low min server memory.

    The only way to get memory allocated at startup is to use large pages, which I absolutely do not recommend doing without a damn good reason and a lot of testing.

    Then why does setting a stupid minimum slow down startup?

    No idea. It shouldn't.

    Haven't got a machine with enough memory to test it out on.

    Yeah, it's been a while since I ignorantly did this on a large scale machine. There may have been other issues at play as well.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning