We are writing tons of data to SQL 24/7. I won't explain why, but suffice it to say our databases are in the 500 to 1000 GB size, legitimately. We have many setups like this. For some reason they have decided to give 32GB RAM to SQL and leave 32 GB RAM to the OS. Basically the database records tons of transactional entries for data that is coming in and then we store that data on the bulk iSCSI SAN storage. They think that 32GB RAM for the OS helps it transmit data to the storage. Ironically their page file is maxed out on every system which means there's not enough RAM right? How do I determine if the OS really needs that much RAM and how do I determine how much RAM to provide SQL. I know the server will take as much as you configure it to use (SQL 2008 R2) so I can't add RAM and then see "hey SQL is only using 75%. Looks like we provided enough!"

Giving around 6 to 8 GB to the OS should be sufficient. Thanks, MadhurjyaMadhurjya Bora OS performance Team, MSFT

Thanks. But what is that number based on? Is there a perfmon number I can look at to see what to use? The page file is maxed out (system managed size). This is on Windows Server 2008 R2 Enterprise x64. Thanks.

Hello, i suggest that you use the SQL server forum where the SQL specialists are answering: http://social.technet.microsoft.com/Forums/en-US/category/sqlserverBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.