• Wilfred van Dijk (5/27/2008)


    You need AWE to prevent memory stealing by the OS.

    Also make sure you have a minimum and maximum size. Don't set the maximum size to unlimited, or SQL will compete with your OS for the last MBs.

    We have the same configuration and our max memorysize is 28GB (min size is 16GB)

    Also, be aware of memory trashing if you do a large OS filecopy on that server.

    You also get memory messages in your logfile when adding/deleting databases/snapshots, but these are ok.

    Memory stealing is not a concern, unless there are other non-OS essential apps running on the server, correct? (I'm thinking Exchange for example).

    Are there other occasions where mem stealing would be an issue?

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]