You are currently browsing the Blog weblog archives for October, 2008.
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
| « Aug | Nov » | |||||
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | 31 | |
- IIS (1)
- Open Source (1)
- Performance (3)
- Personal (2)
- Powershell (1)
- SQL (1)
- SQL Server (20)
- T-SQL (14)
- Uncategorized (6)
- Utilities (4)
- Windows OS (13)
- 23. August 2010: Alert for long-running SQL datbase backups
- 7. April 2010: Learning SMO & Powershell
- 25. February 2010: SQL Generators for moving database files
- 28. January 2010: Index to Filegroup mapping
- 20. January 2010: PowerShell Script to Clean Up Old Files Based on Age
- 7. January 2010: Quick & Dirty way to identify orphan files
- 29. July 2009: Trigger Mass Enable / Disable
- 29. June 2009: Moving Master and Resource databases
- 11. June 2009: Quick and Dirty CSV import to SQL Server
- 2. February 2009: Getting data file space usage
Archive for October 2008
SQL Server “Max Server Memory” Config Value
6. October 2008 by Bennett.
I learned an interesting tidbit while reading Inside Microsoft SQL Server 2005: Query Tuning and Optimization. The Max Server Memory configuration value applies to the cache buffer pool and not SQL Server as a whole. Here is a link to an MSDN article that explains it: http://msdn.microsoft.com/en-us/library/ms180797.aspx
This book goes on to discuss how to detect, measure, and remedy various forms memory pressure. I followed some of the examples in the book and came up with these statistics on one server:
One thing that is kind of interesting about these statistics is that it clearly shows that the configured server memory is significantly less than the memory used by sqlserver.exe.
Posted in SQL Server | Print | No Comments »